Support FlashWindowEx() about console HOT 6 CLOSED

Hello,

This is a pure GUI state.
There is no easy way to detect this state.

from console.

Hi,

Can't the "flash window" event be intercepted for the underlying console
window? Say, something along the lines of

http://stackoverflow.com/questions/7785334/capture-flashwindowex-event-of-a-running-process-c

On Wed, Oct 30, 2013 at 6:15 PM, Christophe Bucher <[email protected]

wrote:

Hello,

This is a pure GUI state.
There is no easy way to detect this state.

—
Reply to this email directly or view it on GitHub.

from console.

No it cannot. There is no event and no window message.

Hook a call to FlashWindowEx implies an injection in the process which calls FlashWindowEx.
ConsoleZ injects code only in the shell launched.

You can use another GUI function to notify the user.
Or display some text to notify the user (the more natural way in a console application)

from console.

It's the "shell launched" that calls FlashWindowEx.

And while "displaying text" is natural indeed, it is hardly the only way to interact with the user.

Case in point: this shell flashes its console window after a long command has completed -- very useful when waiting for a build.

I could achieve this effect by running the build with redirected stdout and stderr, and relying on Console's built-in ability to flash tabs when they display new text (in this case: when a new prompt is shown). But this is obviously less comfortable...

from console.

I will not code a labyrinthine system just for one program.

There are many ways to do a visual notification.
C:\Windows\System32\msg.exe %USERNAME% "complete"

from console.

On Thu, Oct 31, 2013 at 6:42 PM, Christophe Bucher <[email protected]

wrote:

I will not code a labyrinthine system just for one program.

I expected this would be one more injection/interception into the spawned
shell, right next to the others.
I still fail to see the "labyrinth", but I will obviously accept your
judgement here.

Saying "just one program" is most probably wrong technically and clearly
wrong as an attitude.
I think the correct way of saying this is something like "Console2 supports
(and enhances) most of the features of the windows terminal window;
however, a few minor things don't work -- some cannot be justified in terms
of effort/gain, others might be downright impossible to support".

There are many ways to do a visual notification.

C:\Windows\System32\msg.exe %USERNAME% "complete"

Of course there are.
The one I talked about is simply the best fit for some type of situations
(I guess this is why they invented it).
It would have been nice if Console supported it out of the box (like it
does many things), and that's why I created this issue; bit if that's not
possible, I can of course live without.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/48#issuecomment-27502804
.

from console.