|
Post Reply
eric 2008-07-06 05:46
I have a few ultramon shortcuts that maximize on monitor 2. There appears to be a race condition, since in most cases now (but not all) launching via this shortcut will maximize on monitor 2 but then immediately minimize again.
I'm running with 2.6 and I have just upgraded my motherboard which has a faster processor. This problem did not appear previously. So, I am guessing that by running faster, I've run into some bug.
I am wondering if the more recent versions address this issue or if I'm the first to bring up this issue. I'd just as soon stay with 2.6 if this issue isn't fixed in later versions.
|
Christian Studer 2008-07-06 10:41
Does this happen with all applications, for example also with Notepad?
Christian Studer - www.realtimesoft.com
|
eric 2008-07-07 11:17
I only have a couple of UM shortcuts set up, and the one that does this is firefox. I also have a similar one for internet explorer, and it doesn't happen with that.
Ironically, firefox has become the slower of the two browsers at starting up, so I wonder if this problem is related to that.
And if I launch a second, third, ... instance of firefox, it does not happen either. Only the first one, which does take more time to get started up has this problem.
Oh, I installed version 2.7.1 and this did not change the behavior here.
|
Christian Studer 2008-07-07 12:38
Does it work correctly if you set Show to Normal instead of Maximized?
The reason you don't see the issue with the additional instances is that UltraMon can only position the first Firefox instance.
Christian Studer - www.realtimesoft.com
|
eric 2008-07-08 05:01
Changing over to normal and launching about 20 times and I didn't see the problem. But I do see something that is puzzling in either setting.
Sometimes on the launch, I see firefox do a minimize after the window flashes on the monitor for a split second, then another split second later (maybe 1/10th sec) it maximizes again.
Do you have some sort of built in wait before you adjust the window? If so, that could explain why this appears to be racing. But I can't see why firefox would be trying to minimize on it's own.
I wonder if sysinternals has some sort of trace I could put on this and see just what windowing requests are made. If I find something, I'll report back any results.
|
Christian Studer 2008-07-08 12:47
UltraMon tries to determine which window created by the application is the main window, and will then move that window.
This shouldn't cause any problems though, and I don't know why the window would get minimized, it's unlikely that this would be caused by UltraMon.
Christian Studer - www.realtimesoft.com
|
Post Reply
|
