User forums > Nightly builds
The 12.11 RC1 (11 November 2012 build 8549) is out.
dmoore:
--- Quote from: MortenMacFly on November 20, 2012, 07:06:05 pm ---
--- Quote from: dmoore on November 20, 2012, 06:56:54 pm ---I can't actually replicate the issue... What is the problem that this is solving? (and how do I reproduce?)
--- End quote ---
- have a project with many files (with dummy content)
- run a "Replace in files" operation
- make sure things get replaces and e.g. editors are open whose content is updated
-> after the operation has finished (and editors were opened) C::B seems like "dead", an UI refresh seems missing.
--- End quote ---
Thanks. I can replicate the issue but the patch doesn't appear to fix. (Perhaps opening the new window while the UI is frozen causes a problem with something like AUI?) Why do we need to freeze the app anyway?
Folco:
When I run a project from CB (the green arrow in the compiler toolbar), and that I kill this program, I can't stop the debuger anymore.
I get that :
The red cross of the compiler toolbar doesn't work, and the icons of the dbg one bring the dialog box you see.
The only way to stop the debuger is to stop CB.
I get that with Win 7 64b, MinGW (not the one provided with CB) and gcc 4.7.2.
MortenMacFly:
--- Quote from: dmoore on November 20, 2012, 07:38:02 pm ---Why do we need to freeze the app anyway?
--- End quote ---
Yes, that came to my mind, too. Initially it was done to speed up things - but I think a Hide() / Show() call instead might be better... Can you try tat?
raynebc:
Since it's been this way for a while, I figured I'd mention it since this is a release candidate: Often, I notice that when building my project, the build log display doesn't refresh properly, I have to toggle it off and then back on with F2 and then it will display its progress.
dmoore:
--- Quote from: MortenMacFly on November 20, 2012, 08:41:22 pm ---
--- Quote from: dmoore on November 20, 2012, 07:38:02 pm ---Why do we need to freeze the app anyway?
--- End quote ---
Yes, that came to my mind, too. Initially it was done to speed up things - but I think a Hide() / Show() call instead might be better... Can you try tat?
--- End quote ---
It works but it's a little weird visually to have the app disapper then come back. (Just dropping the Freeze/Thaw also works, but I guess it could be really slow if there were a huge number of changes)
Changing topic: opening and closing the CB project file is still slow as molasses... Are we not touching this until after release?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version