User forums > Help
New File shutdown
Michael:
--- Quote from: thomas on May 03, 2006, 12:59:53 pm ---
--- Quote from: kkez on May 03, 2006, 11:21:17 am ---I found how to reproduce it:
[...]
--- End quote ---
Works just fine for me. No matter what voodoo I try, there is nothing that looks queer.
--- End quote ---
Hello,
I have also tried and it works fine for me too.
Best wishes,
Michael
PS.: Interesting signature... :D
Vampyre_Dark:
Okay I think I understand what is going on now. Currently if I have some apps opened, and I open CB from my quick launch and go back to work in my other windows, CB doesn't go onto the task bar until it is completely finished all it's start up tasks. When it was trying to forever load my default workspace, it meant no icon at all because it never finished. Make sense?
I have opened and closed it some 30 times since yesterday, and this seems to be the case every time.
Right clicking in the workspace pane and saving my workspace did the trick to get the program to open it on startup. There should be a MAKE DEFAULT option in there.
kkez:
See this flash video.
If you minimize/restore firefox by double clicking on its taskbar button, everything is fine.
thomas:
--- Quote from: Vampyre_Dark on May 03, 2006, 02:52:08 pm ---CB doesn't go onto the task bar until it is completely finished all it's start up tasks.
--- End quote ---
But that is perfectly normal, it is supposed to do that :)
To avoid mindless overdraw, we do not show the main frame until everything is initialised. The splash screen does not show in the task bar, but this, too, is intentional.
If you look closely at Code::Blocks RC2 (which does not retain the main window), you see that the complete UI is redrawn at least 20 times during startup. wxWidgets is particularly braindead when it comes to event handling, especially regarding UI updates. In fact, I often wonder that despite this, Code::Blocks is still usable at all.
If you are in for a good laugh, set a breakpoint in some function handling UpdateUI events, and count how many times it is called if you just move your mouse a tiny bit. For example, if you move your mouse over the middle of the editor (no way near the menu bar), you can be lucky enough to get 6-8 UpdateUI events for the file and the edit menu. Luckily, you have plenty of CPU cycles to burn :)
Nota bene: Actually, this might be one reason for the high CPU load problems reported with Xorg.
MortenMacFly:
--- Quote from: kkez on May 03, 2006, 03:50:11 pm ---See this flash video.
--- End quote ---
I can't reproduce it on my machine doing the same steps as you did. Anway: Just a wild guess: Could you try to disable the keybinder plugin (and maybe others...?!) and see if this changes something?
With regards, Morten.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version