how to get to a dialog window that won't come into focus by using the keyboard?

[cranioscopical]

is there no end to this quest?

-nudone (May 14, 2010, 11:11 AM)

Yes, it's "ion". 

Good luck with WiLMA, it seems a good match with your layout.
(You may find you have to suspend AWM in some cases but that can be automatic.)

Thanks for all the info you're posting here. You're on an interesting journey.

[nudone]

i'm glad someone else is finding it interesting.

when you say AWM can be suspended automatically, do you mean it will suspend operation when a specific window has focus? i'd seen how you can set rules/exclusions but not a "global" kind of suspend.

[lanux128]

also there is a Actual Window Manager mini review by tranglos.

[nudone]

also there is a Actual Window Manager mini review by tranglos.

-lanux128 (May 14, 2010, 11:28 AM)

oh right. i didn't know that either. i must have brushed past it when i wasn't after such a tool. thanks, lanux128.

[cranioscopical]

when you say AWM can be suspended automatically, do you mean it will suspend operation when a specific window has focus? i'd seen how you can set rules/exclusions but not a "global" kind of suspend.

-nudone (May 14, 2010, 11:27 AM)

Oh, sorry, no.
I meant only that you, yourself, could set up however you call WiLMA to switch off AWM.

[nudone]

oh right. that's intersting though. if WiLMA can disable things then that does open up possibilities.

[cranioscopical]

oh right. that's intersting though. if WiLMA can disable things then that does open up possibilities.

-nudone (May 14, 2010, 12:14 PM)

Oh dear, sorry again, I must learn to express myself better. 
I don't think WiLMA will do that, so you'd just call WiLMA by launching something (of your own): step 1 stop AWM, step 2 start WiLMA -- batch file, a line or two of ahk, whatever. You'll need to see if you need that, and what if any interactions you have on your system, and what works best for you.

[nudone]

oooohhh. i see. well, thanks for clarifying that.

[lanux128]

this is a newer version of this script. the changes are ini file support for adding new windows/dialogs to be watched and tray menu customization. please give it a try.

[nudone]

thanks very much, lanux128.

i've commented out the tooltip in the loop as it wouldn't stop floating around my cursor when it appeared.

is it a complicate addition to make the loop perform different actions depending on which window is activated?

currently it works fine for me - as the "Yes" button is always the one to click in the dialogs used. but i expect this will not always be the case.

here's the current script.

Code: AutoIt [Select]

1. #Persistent
2. #SingleInstance force
3. #NoEnv
4. ;#NoTrayIcon
5. SetBatchLines, -1
6. SetTitleMatchMode, 2    ; partial title match
7. SetWorkingDir, %A_ScriptDir%
8. DetectHiddenWindows, Off ; they are hidden for a reason..
9.  
10. Gosub, Get_INI              ; go to INI section
11. IfExist, %TrayIcon%         ;TrayMenu Customisation
12.   Menu, Tray, Icon, %TrayIcon%
13.   Menu, Tray, Tip, Activate the specified window/dialog whenever it appears.
14. SetTimer, ActivateMe, 500   ; timer starts - increase or decrease the value as necessary
15. Return
16.  
17. ActivateMe:
18. ;parse and auto-activate
19. Loop, Parse, WatchThese, |
20. {
21.         ;Tooltip, %A_LoopField%
22.         IfWinExist %A_LoopField%
23.         {    
24.                 WinActivate    ;do something here like press the ok button
25.                 ControlClick, Yes
26.                 ;sleep for a while - good for cpu cycle
27.                 Sleep, 2000
28.         }
29. }
30. Return
31.  
32. Get_INI:
33. If (!FileExist("ActivateDialogs.ini")) ;if the ini file doesn't exist, create it with the info below
34. {
35.         FileAppend, [Settings]`nWatchThese=File has changed ahk_class #32770|Delete Shortcut ahk_class #32770`nTrayIcon=Application-warn.ico, ActivateDialogs.ini
36. }
37.  
38. IniRead,WatchThese,ActivateDialogs.ini,Settings,WatchThese
39. IniRead,TrayIcon,ActivateDialogs.ini,Settings,TrayIcon
40.  
41. Return

[lanux128]

thanks very much, lanux128.

i've commented out the tooltip in the loop as it wouldn't stop floating around my cursor when it appeared.

is it a complicate addition to make the loop perform different actions depending on which window is activated?

currently it works fine for me - as the "Yes" button is always the one to click in the dialogs used. but i expect this will not always be the case.

-nudone (May 31, 2010, 05:18 AM)

ah, apologies for the tooltip, it's a left-over debug tool..

yes you can perform different actions based on the activated window, put something like this in the inner loop (lines 24-27).

Code: AutoIt [Select]

1. If A_LoopField = metapad ahk_class metapad
2.     MsgBox The metapad window is detected.
3. Else If A_LoopField = ahk_class notepad
4. {
5.         ;notepad window - let's do something else
6.         WinActivate
7.         ;do something else
8. }

[nudone]

thanks, lanux128. that works great. i think that is going to come in very handy now.

[lanux128]

you're welcome..