Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Busy mouse pointer

vefatica

vefatica

May
13,834
211
When TCC is in WT ...

Dismissing MSGBOX (with a click) leaves the busy mouse pointer (spinning blue wheel). And dismissing the [dir]history popup (with Esc) while the mouse pointer is in popup's text area does the same. I fought that phenomenon with only modest success with WinEvent hooks and a WiggleMouse function.
 
I couldn't reproduce it with PWSH (Google AI told me how to make a message box in PWSH) or with this (65552 = 0x10010 is the owner of TCC's MSGBOXs).

Code: 
echo %@winapi[user32,MessageBoxW,65552,"foo","foo",0]

It doesn't happen if I do this in TCC.

Code: 
pshell /s "Add-Type -AssemblyName PresentationFramework ; [System.Windows.MessageBox]::Show('Hello')"

The busy pointer is rock-solid behavior for TCC's (in WT) MSGBOX.
 
And it doesn't happen with TCC v27.

And it does happen with TCC v28.

both in WT, no plugins
 
Is TCC setting the dialog's parent to the console window? I suspect that Windows may restore the focus to the parent window when a dialog closes.
 
Charles Dye said:
Is TCC setting the dialog's parent to the console window? I suspect that Windows may restore the focus to the parent window when a dialog closes.
Click to expand...
I had some beeps in my WinEvent hooks in the 4WT plugin to (try to) figure out what was going on. IIRC, The GetConsoleWindow window was getting foreground when the OPTION dialog closed and not when the history popups were closed.
 
vefatica said:
I had some beeps in my WinEvent hooks in the 4WT plugin to (try to) figure out what was going on. IIRC, The GetConsoleWindow window was getting foreground when the OPTION dialog closed and not when the history popups were closed.
Click to expand...
That is not happening any more (build 24 I reckon) with the OPTION dialog, history popups, MSGBOX, or @SELECT. If the mouse pointer is in any of those when they're dismissed I get the busy pointer.
 
Does anyone else see this (no one has said so)? It's the spinning blue wheel without an arrow. I think it's called a "throbber".

The TCC/WT combination is pretty good at showing it (every time as discussed earlier) but I can reproduce it without TCC.

I can reproduce it with TaskScheduler (and other system apps, but not at all dependably) by dragging a task's properties dialog onto the WT window, leaving the mouse in it and pressing <Esc>.
 
I tried that with a task properties dialog ... didn't saw a busy mouse pointer.

Till now, I could only see that right after I started a TCC session (first try maybe 1 sec, further starts maybe 0.2 sec or so).
 
You must log in or register to reply here.
Back
Top