firefox moves from secondary monitor to main monitor when alt-tab out of game on main? - firefox

so i play a game on main monitor, watch films in firefox(1) on secondary, have game-related research on firefox(2) on main.
if i alt-tab from game to the firefox(2) then firefox(1) moves itself to main monitor which is kinda annoying, especially if i'm going back and forward repeatedly...
best i could find on google is here but no answers given
any idea what's going on, or how to keep the firefox window on the monitor i put it on?
don't know if it's relevant but monitor 1 is displayport, 2 is hdmi
thanks

Related

Mouse/keyboard probably hacked

I recently played a game called "Quake Champions" from Steam. Against a player I know for a fact is a cheater, my left mouse button stopped to work whenever he was in a close-radius.
I am sure it is a cheat because my mouse works just fine on other computers.
I heard of DLL injection and cheaters using such methods. I am afraid somehow my mouse and maybe keyboard are being monitored remotely.
What can I do to find out, and also solve the issue ?
I tried re-installing display drivers, full game and deleted all files, mouse driver and app (mouse is Razer Basilisk Essential), I tried anti-malware softwares, etc.
Now even outside of the game the mouse seems to skip clicks at times, especially when I hold and drag (continuous fire in the game...).
I documented myself a bit and heard of hooks. I would ideally like to figure out which process (visible or not in task manager) hooks or interacts with both my keyboard and mouse, it would probably be a great way to figure out if I am in trouble or not.
Formatting the computer in full IS an option, but one I would prefer to avoid as I have costly licenses that I may lose, due to a limited number of activations...
Any help appreciated.
Further info:
Razer Central/Synapse -> Keyboard: Razer Cynosa Chroma ; Mouse: Razer Basilisk Essential
Further anxiety:
Shortly after this event happened, I received an alert from my Facebook saying somebody tried to log in... It was not me. It may be a coincidence, it may not. Fortunately my Facebook password is strong enough. But this is further reasons to be anxious on my end...

Secondary touch monitor not moving with the cursor but still pressing buttons (or emitting events for Qt app)

I intend to make an app for Windows in Qt with multi-monitor support, one (secondary) monitor being touch. I want one person to be able to work with the touch screen independently on a second person, which would be working on the main screen with mouse and keyboard.
I don't have the the touch monitor yet, so I don't know how it really works, but I am afraid that touching the monitor would move the cursor (mouse pointer), making the work with mouse very hard.
So my question:
Is it possible somehow to make the touch screen not to affect the cursor in any way (not interrupting drag&drop counts, too), but still to be able to push buttons n' stuff, and that on either Windows or Qt level?
No buttons pushing, but generating QTouchEvents (or similar) would be sufficent, too.
Thanks for your responses.

Turn off computer when screen is powered down ( windows 7)

Mostly out of curiosity, i was wondering how should i approach this. I'd like to make it so that when i turn off my screen, the computer shuts down. In essence, i'd like to make a service that constantly check whether the screen is on or off.
Any ideas/suggestions are welcome. Thank you for taking the time and i wish you all a plesant day.
Well, if there would be a way to check the status of the connected monitors and you shut your computer down when the screen goes off, how do you plan to turn your computer on again? I expect then you have to use the normal hardware button on your tower. Why not stick to these buttons? It has worked the last 30 years or so...
To make an actual suggestion:
Setup a webcam to monitor your screen. Using simple picture analysis you can detect if the screen is on or off
Shutdown your computer down when screen goes off
Also you can monitor the szenario when turning your screen on. You should see a manufacturers logo for a few seconds or somethinglike this. (Now you need a second computer with a second webcam)
With the second computer you can build some little machine that pushes the power on button on your first computer to turn it on
But how to turn on/off the second computer? Well, you need another one for that...

discontinuous BitBlt capture

I am using BitBlt heavily in my project. I create a number of threads and in each thread I capture the screen by BitBlt. It works great and as expected for now except the following problem.
The problem happens when the user clicks on a running program or for example already opened explorer on the taskbar. You know when you click on the running program on the taskbar, it either minimizes or appears on the screen. The issue that I am talking about happens just in this transition. At that moment, something like an interrupt, all threads stop capturing the screen for a fraction of a second and then they continue capturing. The same thing happen when you move down or up the thing on the volume control window. Could you please shed some light why this is happening and how I can prevent this happening?
Thanks.
Jay
It could be a scheduling issue. When you activate an app, it gets a small, momentary boost in its priority (so that it can seem responsive in the UI). This boost might last about as long as the animation and momentarily pre-empt your screen capture threads.
It's also possible that the desktop manager is serializing stuff, and your bitblts are simply stalled until the animation is over. Even if you've turned Aero off, I believe the desktop window manager may still be in compositing mode, which has the effect Hans Passant was describing in the comments.
If you're trying to make a video from the screen, I think it's going to be impossible to rely on GDI. I strongly suggest reading about the Desktop Window Manager. For example, this caveat directly applies to what you're trying to do:
Avoid reading from or writing to a display DC. Although supported by DWM, we do not recommend it because of decreased performance.
When you use GDI to try to read the screen, DWM has to stop what it's doing, possibly render a fresh copy of the desktop to video memory, and to copy data from video memory back to system memory. It's possible that the DWM treats these as lower-priority requests than an animation in progress, so by the time it responds to the BitBlt, the animation is over.
This question suggests that DirectShow with a screen capture filter might be the way to go.

multiple monitor support in application

What does it mean by multiple monitor support for an application?
In the old days computers only ever had a single screen attached. Now they often have more than one attached and a desktop that spans those screens.
You need to make sure that your app:
Maximises to the monitor that it is most closely associated. A badly written app might always maximise a window to the primary monitor.
Remember which monitor it was displayed on when last run, and restore to that monitor when it starts up again.
Avoid displaying on a monitor that is no longer available. For example, consider a laptop with an attached screen. If you show the window at coordinates for a screen that has been disconnected (e.g. laptop user on the move) then they won't be able to see it.
It all depends on the application.
For some applications it just means that that you could open a very big window.
For others it might mean that you could open two windows, one for each monitor. For example, Lightroom, lets you view a collection of thumbnails on one window and a full-sized image on the other.

Resources