@killerbot : does the batchbuild work with this NB ?
* Special pre/post build command added: #run_script. Usage: "#run_script filename.script". Allows to run a Code::Blocks script during the build process. A usage example will be posted on the wiki soon.
* New script function: InstallPlugin(). When called from a script, a security warning is emitted (no way to turn this off).
* Fixed minor bug in build scripts clearing.
* Few more macros added in MacrosManager:
- TARGET_OUTPUT_FILE: active target's output filename.
- TARGET_OUTPUT_BASENAME: active target's output base name (no path and no extension).
- [target_name]_OUTPUT_BASENAME: named target's output base name (no path and no extension).
i thought when you've built it, you can test it also :shock:@killerbot : does the batchbuild work with this NB ?no idea (I still build from within CB ...), still not automated, always postponing it ...
i thought when you've built it, you can test it also :shock:...unless he doesn't like C::B to integrate into explorer... ;-)
Do you use the nightly or a self-build variant?guess
there are so many features to test, if I need to test them all, well then it's already time for the next nightly ;-)yeah, i don't expect that you test every feature before you release a NB,
Pls put one of those night builds as a RC3 build. That is not trivial task for new users to install C::B from night builds. Specially the RC2 is a lot worse then Night Builds.... :?I guess this would be a bad idea. Now we have the one or other user that doesn't read through the webpage/forum/wiki where are written several article several times on how to install a nightly build (you basically need to extract it in an empty folder and that's it - where's the problem?).
there are so many features to test, if I need to test them all, well then it's already time for the next nightly ;-)yeah, i don't expect that you test every feature before you release a NB,
but when i ask you for a specific test, it should be doable, isn't it ?
you answered already in the other thread,
so many thanks !
brgds, tiwag
but your request came after the nightly was kicked out :?
ERROR: Plugin resource not found: compilergcc.zip
ERROR: Plugin resource not found: debuggergdb.zip
ERROR: Plugin resource not found: pluginwizard.zip
It's reproducible (at least for me) by opening as much files as are needed in order to get at least two pages of tabs in the tabs pane (so you need to use the arrows to the right in the tabs pane to switch between the pages). Select a page and a tab, change to a different page, then move the mouse pointer inside the tab pane, followed by moving the mouse pointer anywhere outside the tabs pane. At this point, the "X" button from the previous page becomes visible on the current page at the same location, but it's (thankfully) not clickable.
I'm using todays build (unicode) and windows XP sp2. I've tried all the different tab "skin" flavours available in the environment options dialog and get the same results with each one of them. Hope this helps.
Yesterday I have a powerbreak (linux, fc4) and since CB pupup a yellow balloon after every startup:
"Some errors have been logged during the Code::Block startup process."
But the C::B is running fine. Where is this log file? I not found this.
In the "Messages" window upper right hand side is triangle < that you need to click on to see the tabs on the far left.
Debugger does not work for me (linux, fc4). It`s ignore all breakpoint.
It's reproducible (at least for me) by opening as much files as are needed in order to get at least two pages of tabs in the tabs pane (so you need to use the arrows to the right in the tabs pane to switch between the pages). Select a page and a tab, change to a different page, then move the mouse pointer inside the tab pane, followed by moving the mouse pointer anywhere outside the tabs pane. At this point, the "X" button from the previous page becomes visible on the current page at the same location, but it's (thankfully) not clickable.
I'm using todays build (unicode) and windows XP sp2. I've tried all the different tab "skin" flavours available in the environment options dialog and get the same results with each one of them. Hope this helps.
I think this one falls under my domain :)
Thanks for the step-by-step information for how to reproduce the bug, I will have a look at it later today.
Eran