Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: kisoft on November 18, 2005, 11:33:14 am
-
I download CVS version C::B now. Build (NewBuild.cbp). Remove "Old" contrib plugins, and found next:
1. On try check off Debugger toolbar (for example), C::B take a fall down (see screenshot).
2. After normal exit, don't save workspace. On next start C::B, workspace is empty.
Very impressive, great work, many hot wanted changes!
Testing is continued.
Tested on Win2k only, on SuSE can't test now.
[attachment deleted by admin]
-
2. After normal exit, don't save workspace. On next start C::B, workspace is empty.
I get this also, C::B isn't using the default workspace anymore :(
Also when I add a file to a project I get an Unhandled exeption.
-
2. After normal exit, don't save workspace. On next start C::B, workspace is empty.
I get this also, C::B isn't using the default workspace anymore :(
The configuration settings are handled differently now, and unfortunately they aren't translated from the old ones. This means all settings have reverted to defaults, and the default in this case seems to be to start in a blank workspace.
You can change this by selecting "Open default workspace" in Settings -> Environment -> View.
-
...
The configuration settings are handled differently now, and unfortunately they aren't translated from the old ones. This means all settings have reverted to defaults, and the default in this case seems to be to start in a blank workspace.
...
:oops: thanks!
Now found another bit data:
Choose menu: Tools/Configure tools/Add
After input datas, on press Ok button, I see "Unhandled exception". After it, on press Close button, I see Unhandled exeption again.
Test drive being continued..
PS Ctrl-RMB - search on Google, funny :) For lazy men, hmm, go to C::B forum need :wink: or send bug report, all right, it's for contrib plugin.
-
"Unhandled exception" does not tell an awful lot. Normally, exceptions come with a detailled description about what is wrong. Sometimes, that alert is only shown when the application is closed (seems to be a quirk in the exception handling code?).
Is there no information except "Unhandled exception"?
-
"Unhandled exception" does not tell an awful lot. Normally, exceptions come with a detailled description about what is wrong. Sometimes, that alert is only shown when the application is closed (seems to be a quirk in the exception handling code?).
Is there no information except "Unhandled exception"?
You right, exception must have additional info. But it's Unhandled exception.
Look screenshot for explains.
[attachment deleted by admin]
-
Choose menu: Tools/Configure tools/Add
After input datas, on press Ok button, I see "Unhandled exception". After it, on press Close button, I see Unhandled exeption again.
I 've seen it today too. I 'm looking into it...
-
Done, fixed in CVS.
-
Done, fixed in CVS.
Being wait.
Very very big thanks the Good Man, than create ContribPlugins.workspace,
and The Men (or The Man) than created *-NewBuild.cbp for contrib projects.
I rebuild this workspace now, I enjoy it! 8)
-
So, next for Tools shortcuts.
Bug:
1. I added new tool to the Tools menu.
2. Settings/Keyboard shortcuts.
3. I selected my new created tool.
4. I pressed Ctrl-F12 (for ex.) on a new shortcut field
5. I pressed the Add button
6. After some seconds C::B fall down (see screenshot)
After restart C::B, I set shortcut without problem. Shortcut is worked.
Bug reproduced 100%, I repeat this work now.
[attachment deleted by admin]
-
This is a known problem with keybinder. It assumes that all application windows are permanent, i.e. won't disappear before app shutdown. Of course this is not the case, mainly for editors. I 'm looking for a workaround. Currently I can only advise to edit shortcuts only when no editors are open (not even the "Start here" page)...
-
Bug on edititing compiler properties:
1. Settings/Compiler, choose the Programs page.
2. On "Program Files" page try input any program name by button. For ex. Debugger.
3. After directory selection, a program name saved without path.
See screenshots.
On direct input - all right.
[attachment deleted by admin]
-
Bug on edititing compiler properties:
1) This is not a bug. It's designed behaviour. If you want to use binaries from other paths than the master path, add them in "Additional paths".
2) Trying to specify a debugger other than gdb.exe for gcc or cdb.exe/ntsd.exe for MSVCTK is not going to get you anywhere...
3) You 're mixing bugs in a single topic and this is *not* the place to post bug reports after all. Please use SF trackers to post bug reports...