On Thu, Apr 10, 2014 at 01:12:29PM +0100, Olly Betts wrote:
> On Thu, Apr 10, 2014 at 04:59:25AM -0700, Vincent Cheng wrote:
> > My understanding is that upstream is working towards porting
> > codeblocks for wx 3.0, but it's currently not fully stable yet (e.g.
> > #736368).
>
> The issue there is most likely because wx 3.0 enables "WXDEBUG" mode
> by default which includes checks for incorrect API usage, whereas with
> wx 2.8 you had to specify it explicitly when you built the library. In
> other words, codeblocks is misusing the wx API, but with 2.8 this gets
> quietly ignored by default, whereas 3.0 reports it by default.
I just tried to reproduce the issue described in #736368 using my
13.12-3.1 build, but I couldn't follow the steps described:
| If I open a .c file,
Ctrl+O and enter a path to a C file - OK
| double click on a variable to mark it,
Double click on a variable in the pane with the source code in - OK.
| right click
Menu appears - OK.
| and selects from the menu "permanentely highlight variable"
There's no such entry in the menu I have (or in any of its submenus).
Cheers,
Olly
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
