User forums > Nightly builds
The 17 August 2009 build (5731) is out.
nix_BB:
This Ctrl-Tab thing is a pain, but I'm experiencing another anomaly that no one else has mentioned yet, so I might be alone here.
A single Ctrl-Tab doesn't switch tabs it only shows the tab dialog. Once the dialog is displayed subsequent commands switches documents forward or backward.
The browse tracker plugin works nicely but it's not a solution to this problem. Ctrl-Tab is an expected navigation standard so this bug is easily noticed and creates the perception that C::B is broken (not wxAUI where the problem lies). Therefore I believe the patch jens is suggesting should be applied to the trunk, even if it's only applied to the main document notebook.
@jens I'll be happy to test your patch and help were I can, as long as I can work under your supervision and bug you for some guidance of course :P
Jenna:
--- Quote from: nix_BB on August 20, 2009, 09:06:19 am ---A single Ctrl-Tab doesn't switch tabs it only shows the tab dialog. Once the dialog is displayed subsequent commands switches documents forward or backward.
--- End quote ---
--- Quote from: jens on August 19, 2009, 06:01:59 pm ---You can change the keyboard-shortcut for the switcherdialog with the keybinder-plugin, and/or use "Ctrl+left/right arrow" instead.
--- End quote ---
To make it clear, after changing (or removing) the keyboard-shortcut for the switcher-dialog (Switch Tabs in the View menu) you can use Ctrl-Tab in both directions, but without wrapping and without respecting the tab-order if changed with drag'n'drop.
Jenna:
--- Quote from: jens on August 19, 2009, 06:01:59 pm ---I can create and a patch if anyone is interested in testing and/or improving it.
But be aware that it might never make it into trunk, even if I think we should do so.
--- End quote ---
I uploaded the patch to my server: http://apt.jenslody.de/patches/cbAuiBook_20090728-1.patch.
It should apply clean to linux and windows.
You should use a fresh svn source-tree, or clean the sources and delete the devel and output subdirs to make absolutely sure nothing old remains there.
wxAuiNotebook seems to be under heavy development (again) at the moment.
So I think we (the devs) should discuss if such a change (that breaks the sdk-api, even if it's broken at all after change to wxAuiNotebook) can ever be applied to trunk.
Because reverting (or even fixing) it if the behaviour in wxWidgets changes, will break api again.
But it seems that the wxWidgets api has changed, so that we need many fixes, before we can use a newer wxWidgets, and that changes will most likely break parts of the api, too.
daniloz:
Hi,
I have a problem with my custom toolchain with this nightly build.
I have wrote an interface in C# to run VisualDSP++ from C::B. This interface runs whatever has to be run to build the project and write the messages back to the console using "Console.Write()".
Then, in C::B, I've set "Settings -> Compiler and debugger... -> Global compiler settings -> [the compiler you use] -> Other settings(rightmost tab)" "Compiler logging" to "Full commandline", as usual. However, this time, I don't get anything in the "Build Log".
This was fully working with v8.02, though.
Any clue?
Jenna:
How do you run your program ?
As pre- or post-build step ?
Are you sure it gets started and has output ?
I just tested it with a simple "Hello world"-program, that writes to the console (c++ not c#), and that works without problems.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version