LiveCode Forums

Now, actually I am not (yet) in the situation that I can mess with the guts of the engine. Sooooo... I really need to have a specific bug fixed. How do I a) start looking what might cause it and b) go about fixing it (while I am learning C)

The bug in question is:

http://quality.runrev.com/show_bug.cgi?id=10384

Bottle of Whisk(e)y to the one who helps fixing

Best,

Malte

can you post what the bug is, not everyone has access to the bug database..

Hi s.

Modal dialogue prevents alt tab on windows to get back to LC app

If a modal dialogue is open you can not use alt + Tab on windows to come back to your liveCode application.

Cheers,

Malte

Good God Windows sucks

Looks like this is an issue that was first reported in 2006.
I so do not want to mess with this.
Whisky's tempting, though...

2 bottles then... <g>

From what I can tell, this is standard Windows behaviour when there is a modal dialog open and has nothing to do with Windows.. Either pick a different window type (modeless) or live with it

It's not my busines, but shaosean should get two botles of whisk(e)y

Marek

Actually no, as far as I can see it is not. Or at least there are other Windows programs that can have modals open and can be alt tabbed back to.

Cheers,

Malte

My original report has some more details about how other applications behave. The LiveCode behavior is not standard.

http://quality.runrev.com/show_bug.cgi?id=3865

Again, not everyone has access to the bug database so would you be so kind as to post the content of it?

ShaoSean: everyone should currently have access to the bug database. Previously it was pay-to-read, but that's gone now, so you should be able to create a login, or email support if it doesn't work.

It would be great if someone could figure out what needs to be done to make this work correctly.

The engine doesn't use the Win32 'modal loop' as this isn't compatible with the way the engine works for commands that block (such as ask / answer etc.). Also, the engine supports application and window modality - again something which Win32 doesn't support with the higher-level Modal loop it provides.

In terms of what the current problem is, I'm not entirely sure (despite having looked at it a few times). There are various aspects of Window relationships (child, parent, owner) and the enablement state whose interactions are not clearly documented (on MSDN). Also, the code for window stacking and display in the Windows engine has had so many small corrections for bug-fixes over the years it is now a bit spaghetti like.

So, moving forward on this, if someone can find some example code that is very clear that shows a modal dialog subordinate to a main window without using the Win32 Modal loop functionality and preserves alt-Tab behavior (and other behaviors that are expected!) we can compare with what the engine is doing and see how to apply an appropriate fix.

Quick search on stackOverflow yields this:

http://stackoverflow.com/questions/1405 ... dal-dialog

and in detail this:

http://msdn.microsoft.com/en-us/library ... FilterText

The discussion on SO said if the owner argument is set when using Form.ShowDialog, it does not vanish from the task switcher anymore.

"The Form.ShowDialog method has an optional argument, owner, that can be used to specify a parent-child relationship for a form."

Now, I am not sure if that is used by the engine of course... Please excuse my dumbness there.