Author Topic: wx3.1 trunk context menu in debugger windows does not show up linux mint 18  (Read 540 times)

Offline BlueHazzard

  • Lives here!
  • ****
  • Posts: 1414
Has someone else also the problem of not getting a context menu for the debugger windows in linux wx3.1:
* Call stack
* Breakpoints

Other windows seem to work. Only in the call stack and breakpoints windows i don't get a context menu. Also the double click in the call stack does not switch the frame. It seems that the events are not called...

greetings

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 10117
As I've said on irc - works for me...
<debugger plugin maintainer>
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Online Commaster

  • Multiple posting newcomer
  • *
  • Posts: 69
Ubuntu 16.04.2 (Not exactly Mint, but close. Hope it's still relevant):

wx_2_8_branch: both menu work
wx_3_0_branch: No call stack menu, but watches work
master: No call stack menu, but watches work

offtopic: Also discovered, that konsole is a no go for debugging, tty /dev/... command fails, because it looks like "/dev/?". xterm works fine.
« Last Edit: June 07, 2017, 09:41:11 am by Commaster »

Offline BlueHazzard

  • Lives here!
  • ****
  • Posts: 1414
wx_2_8_branch: both menu work
wx_3_0_branch: No call stack menu, but watches work
master: No call stack menu, but watches work

i see the same behavior. I debugged it a bit, and it seems that the list control does not send any event (at least the handler are never called). At the moment this events are handled dynamically with a "connect" call. I tried to make it static with EVT_XXX macro, but i had no success... Very strange. I have no idea how to fix this, or where to search for this...

Offline BlueHazzard

  • Lives here!
  • ****
  • Posts: 1414
i tested the sample application of wx, and there it works, so there seems to be a problem in the codeblocks code

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 10117
Then you'll have to debug it and tell us why it happens, because I don't see the problem. Is your callstack window docked somewhere or is it floating window?
I'm testing with 3.0.2. I can test with 3.1 if I don't forget later today.
<debugger plugin maintainer>
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline BlueHazzard

  • Lives here!
  • ****
  • Posts: 1414
Some more update on this:
1) This error is with wx3.0, wx3.1 and wx trunk
2) The example application of wx works without problems
3) The event handler function are not been called for the mouse events
4) It makes no difference if i use dynamic or static event binding
5) I have not found any other non working context menu