David Lomas
Всего сообщений: 377
Дата регистрации: 16.03.2006
|
Создано:
26.07.2007 03:38:05
|
 |
I have a network monitoring tool called PingPlotter which runs in the background. I occasionally want to open its main window, and check something, but then return it to the system tray, so I set up minimise on inactive, with a delay of 500ms. I also have a set size and position on startup, so that it is always in the same place.
The problem is that certain feature of PingPlotter open a dialogue box to ask for some information. As soon as they open, AWM senses that the main window is inactive, and the whole thing - dialogue box as well - is sent back to the system tray.
I can't work out any way of defining the rule so that it will allow the dialogue boxes to prevent the main window from being minimised. I tried defining the rule without the window class - i.e. just the name of the executable, but then it tries to apply the startup size and position to all the dialogue boxes too (obviously) and causes them to break (they just disappear from the screen).
Perhaps this is more like a feature request - would it be possible to not auto-minimise if the window has dialogue boxes open?
|
|
|
Michael Rezvanov
Администратор
-retired-
Всего сообщений: 387
Дата регистрации: 31.01.2007
|
Создано:
27.07.2007 02:21:22
|
Thank you for your report David. We will have to test this behavior. We will let you know about the results of our test.
|
|
|
David Lomas
Всего сообщений: 377
Дата регистрации: 16.03.2006
|
Создано:
27.07.2007 05:25:14
|
There's something else odd with the PingPlotter application too. I've created a rule which only has a 'change position at startup' element - no auto-minimise or anything else.
The application itself appears to remember its previous size/position, and so if the window opens already in the right place, the AWM rule causes the window to vanish. It is still running, and a 'minimise / restore' cycle via the taskbar brings it back.
If I move the window before quitting the app, when I start it again, it opens momentarily where I left it and then AWM moves it to the right place and it stays open. But if I don't move it before I quit it, starting it again causes it to vanish!
Hope that makes sense - I'm using AWM 5b1 by the way - perhaps this should be on the Beta testing forum - sorry 
|
|
|
David Lomas
Всего сообщений: 377
Дата регистрации: 16.03.2006
|
Создано:
27.07.2007 05:31:48
|
Sorry - this is not limited to PingPlotter - I can reproduce this behaviour with Notepad too. Here's the recipe:
1. Open Notepad and create a specific rule
2. Select the position at startup and drag the target to the current notepad window
3. Save the rule and quit Notepad
4. Restart notepad - if it doesn't start in exactly the same place, it will 'jump' to the position you saved. But if you quit and start it again, it should open in the same place, and will then disappear.
Cheers,
Dave.
|
|
|
Michael Rezvanov
Администратор
-retired-
Всего сообщений: 387
Дата регистрации: 31.01.2007
|
Создано:
30.07.2007 03:23:25
|
Could you please send us your current AWM's configuration? Thanks in advance.
|
|
|
David Lomas
Всего сообщений: 377
Дата регистрации: 16.03.2006
|
Создано:
30.07.2007 03:30:46
|
I tried to reply to the copy of that message I received by email - it came from admin@actualtools.com, but it bounces back as undeliverable. Where did you want me to send the config files?
Thanks,
David.
|
|
|
Michael Rezvanov
Администратор
-retired-
Всего сообщений: 387
Дата регистрации: 31.01.2007
|
Создано:
30.07.2007 21:47:14
|
Please send them at
|
|
|
Michael Rezvanov
Администратор
-retired-
Всего сообщений: 387
Дата регистрации: 31.01.2007
|
Создано:
31.07.2007 04:37:56
|
We have finally received the configuration files and tried to reproduce the situation both with the PingPlotter application and with Notepad (on several computers).
Unfortunately the described behavior wasn't detected. I think there outlines a certain conflict with some third -party application. Therefore, David, could you please try to define it?
|
|
|
David Lomas
Всего сообщений: 377
Дата регистрации: 16.03.2006
|
Создано:
31.07.2007 06:02:13
|
|
OK, perhaps here's something which might shed some light on it - I'm not entirely sure, but see what you make of it.
I'm using a dual-monitor setup, so my desktop is 3200x1200 across 2 monitors. If I move notepad to the right-hand monitor and drag the target, I get something like Horizontal 1953 Vertical 267 in the offset boxes of the configuration window. I haven't selected the move-to-monitor option at all, and maybe this is where the problem is. For example, if I move notepad to the left hand monitor and save its position (say, H323xV293), then manually move notepad to the right-hand monitor before exiting, when I start it again it jumps to a position which is H323xV293 on the right-hand monitor (i.e. actually H1923xV323) - not on the left where I saved its position.
The position I saved which causes it to disappear was H1600xV500 - basically aligned to the bottom-left of the right hand monitor (hope that makes sense!). I guess this is because it opens on the right-hand monitor, and then tries to put it 1600 pixel to the right on that monitor, which is actually off the right hand edge of the desktop.
Basically, I think there is some kind of conflict in the way AWM manages positions and multiple monitors. Maybe windows reports multi-monitor setups differently with different graphics adapters, but I would think you either want to use the raw desktop coordinates (in my case, 3200x1200) and forget the move-to-monitor option, or limit the size/position boxes to, in my case, 1600x1200 and enforce the move-to-monitor option.
I also don't want to lose the auto-minimising when a dialogue box is opened and gets the focus issue where this started - do you want me to start a new thread for that?
Thanks,
Dave.
|
|
|
Michael Rezvanov
Администратор
-retired-
Всего сообщений: 387
Дата регистрации: 31.01.2007
|
Создано:
01.08.2007 02:38:48
|
Thank you for your report David.
Could you please specify: what did you try to do? I mean: what results did you try to get?
Using of target has such peculiarities. Therefore you should define the window position in other ways. For example you can select "Move to monitor" or "Save position on exit."
The problem with auto-minimising is added to our to-do list. But the matter is that the focus issue, being Windows peculiarity, is a non-trivial problem, therefore the fix may require pretty much time. Sorry for possible inconveniences.
As a current alternative you can define bigger delay before minimization.
|
|
|
