Hourglass in long operations (project loading)

[killerbot]

Another note:
Why not add the hourglass at the beginning of the function?
It would be only 1 line of code and all switch cases would be affected while now some are skipped.

I assume you are talking about the OpenGeneric. If so, that's not a good place, since the DnD will call OpenGeneric for every file, that means N times creation/destruction of the glass hour. The glass hour is being constructed though in the Dnd before' all the files are being submitted to OpenGeneric.

[iw2nhl]

I assume you are talking about the OpenGeneric.

Yes, I forgot to say that ;-)

If so, that's not a good place, since the DnD will call OpenGeneric for every file, that means N times creation/destruction of the glass hour. The glass hour is being constructed though in the Dnd before' all the files are being submitted to OpenGeneric.

I try to explain better what I mean:
- place the houglass call in both OpenGeneric() and OnDropFiles()
- in OnDropFiles() is ok
- in OpenGeneric() place it at the first lines
- no problem if the function is called several times in OpenGeneric() by OnDropFiles()
From wxWidgets docs (http://www.wxwindows.org/manuals/2.6.3/wx_dialogfunctions.html#wxbeginbusycursor):
These two calls (wxBeginBusyCursor and wxEndBusyCursor) can be nested, and a counter ensures that only the outer calls take effect.
And note that wxBusyCursor works by calling wxBeginBusyCursor in the constructor, and wxEndBusyCursor in the destructor

For the other problem (about OnDropFiles()), it seems to be caused by:

Code

        Freeze();
        Thaw();

because removing them, it is fixed.

[thomas]

1) the hourglass is called, but never shown

Not true. It is shown for a short time, but it is reset soon after. We're not doing it, so send your complaints to Julian Smart.
Moving the call to the beginning of the function does not change the behaviour.

2) the GUI freezes more than before

That's what Freeze() does. However, it avoids the flickering due to overdraw, and it makes loading the dropped files significantly faster, which is one thing you complained about in the first place.

3) while the files are being loaded, you can click on the window below C::B

Don't do that then.

[iw2nhl]

1) the hourglass is called, but never shown

Not true. It is shown for a short time, but it is reset soon after. We're not doing it, so send your complaints to Julian Smart.
Moving the call to the beginning of the function does not change the behaviour.

I don't know Julian Smart, who is him?

2) the GUI freezes more than before

That's what Freeze() does. However, it avoids the flickering due to overdraw, and it makes loading the dropped files significantly faster, which is one thing you complained about in the first place.

I never complained about slow loading, but about no feedback during the slow loading. They are different things ;-)

3) while the files are being loaded, you can click on the window below C::B

Don't do that then.

Probably this was not clear, but this is a bug (probably of wxWidgets).
If I have Firefox loaded below C::B and I move the mouse over C::B window, I see the text which is "highlighted" by the mouse on the HTML page of Firefox (animated images too).
Anyway I think that Freeze() and Thaw() give more troubles than what they solve.

[jmccay]

1) the hourglass is called, but never shown

Not true. It is shown for a short time, but it is reset soon after. We're not doing it, so send your complaints to Julian Smart.
Moving the call to the beginning of the function does not change the behaviour.

I don't know Julian Smart, who is him?

  Just so you know that should be: "who is he".  Julian Smart is the creator of wxWidegts (formerly wxWindows).  I have emailed him a couple of times, and I even got replies.  You might try addressing the behaivor/problem in the wxWidgets forums.

jmccay

[iw2nhl]

  Just so you know that should be: "who is he".

Ok, thanks! I've just learned something more of this language (english). ;-)
[EDIT]
And it's that way because he is the subject, not the object. Right?
[/EDIT]

I found in another forum a problem like this:
http://wxforum.shadonet.com/viewtopic.php?p=33381#33381

If the code between the Freeze & Thaw are expensive, and you for example press the mouse left click - you might ending up pressing on the application under your application.

The best thing to do is to call the frame child's Freeze & thaw.

Do we need to call freeze on all the application?
Can we freeze only needed widgets (like the menu bar)?

Anyway I think that the "Start here" page should be closed _before_ any opening sequence.

[thomas]

Do we need to call freeze on all the application?
Can we freeze only needed widgets (like the menu bar)?

To what avail? The menu bar is not causing any significant overdraw.

[iw2nhl]

Do we need to call freeze on all the application?
Can we freeze only needed widgets (like the menu bar)?

To what avail? The menu bar is not causing any significant overdraw.

1) menubar is _constantly_ redrawn (flickers)
2) that was only an example