Am Tue, 28 May 2013 20:05:32 -0000
schrieb Stephan Haller <email address hidden>:
> Currently I have the idea to create a while-loop which waits for the
> MidoriBrowser (where we will create the infobar at) to get the active
> one. The disadvantage is that it will we CPU intensive (100% cpu
> load). The advantage should be that it should enter our modal main
> loop only if it got the active window - that should only happen if
> the modal window like toolbar editor was closed. I have no idea to
> make it asynchronously to be nice to CPU.
The most simple implementation that came to my mind is to
* check if any dialog is open before the cookie bar is shown
* wait until it is closed (sleeping with 1s interval)
* show our question afterwards
I cannot reproduce it for the preferences window. Can you check what
is the difference to the toolbar dialogue?
Am Tue, 28 May 2013 20:05:32 -0000
schrieb Stephan Haller <email address hidden>:
> Currently I have the idea to create a while-loop which waits for the
> MidoriBrowser (where we will create the infobar at) to get the active
> one. The disadvantage is that it will we CPU intensive (100% cpu
> load). The advantage should be that it should enter our modal main
> loop only if it got the active window - that should only happen if
> the modal window like toolbar editor was closed. I have no idea to
> make it asynchronously to be nice to CPU.
The most simple implementation that came to my mind is to
* check if any dialog is open before the cookie bar is shown
* wait until it is closed (sleeping with 1s interval)
* show our question afterwards
I cannot reproduce it for the preferences window. Can you check what
is the difference to the toolbar dialogue?
All the best,
kardan