[BUG] C::B svn 9115 wx2.9.4 with Ctrl+V and CC too in dual view

[BlueHazzard]

Hello,
i have found a bug in svn 9115 build with wxWidgets 2.9.4

i have two files open (see image). if I copy something from the top window to the bot window it will always be inserted in the top window (Ctrl+V and also with the Menu entries). also if i type in the bot window the cc will start in the top window. The bot window is the second window.

I haven't the time to investigate in this bug, i wanted only to report it.

(I also know that wxWidgets 2.9 port is not stable, but if someone is working on it, this could be useful)
thx

[dmoore]

Slightly O/T, but still related. I don't have time to look at the code, but I think there must have been a recentish change (I'm using rev 9001, wx2.8 ) to copy/paste behavior , because in the past I was able to disable the keybinder plugin shortcuts of Ctrl-C, Ctrl-X and Ctrl-V and get the platform default handling of cut/copy/paste operations, which means Ctrl+C,V,X work in all widgets instead of just the active editor (whose idea was that anyway?). That doesn't work any more -- in fact, I get a message about Keybinder INI corruption if I try to alter the cut/copy/paste shortcuts.

Edit: I'm on wx2.8 not wx2.cool

[oBFusCATed]

The handling of accelerators in wx is super insane and I think they've made it even madder in 2.9

If you have an accelerator for ctrl+c it will override the native control's handlers and this is by design.

[dmoore]

If you have an accelerator for ctrl+c it will override the native control's handlers and this is by design.

But I am on 2.8 and am trying to unset the accelerator, but can't.

[dmoore]

i have two files open (see image). if I copy something from the top window to the bot window it will always be inserted in the top window (Ctrl+V and also with the Menu entries). also if i type in the bot window the cc will start in the top window. The bot window is the second window.

Btw, copy/paste on multiple windows appears to work fine on Rev 9001, wx2.8 (i.e. can't reproduce OP's problem)

[Jenna]

If you have an accelerator for ctrl+c it will override the native control's handlers and this is by design.

But I am on 2.8 and am trying to unset the accelerator, but can't.

Some accelerator related code in keybinder-plugin has changed recently: http://sourceforge.net/p/codeblocks/code/8328/ , I don't know, whether it could have cyused the issue.

Deleting the ini-file, as suggested by the dialog works for me, but all custom settings are lost of course.

[dmoore]

Deleting the ini-file, as suggested by the dialog works for me, but all custom settings are lost of course.

Doesn't work for me. Try clearing the accelerators for cut, copy and paste. Then try adding them back.

[dmoore]

Some accelerator related code in keybinder-plugin has changed recently: http://sourceforge.net/p/codeblocks/code/8328/ , I don't know, whether it could have cyused the issue.

Hmmm... it looks like the most recent changes were actually trying to fix the problem of breaking the native cut/copy/paste accelerators that I was complaining about.

EDIT: after more testing my copy paste problems are actually limited to Tools+ output window (which is a scintilla control), so most likely this is something I have caused    Strangely though, if I remove the copy/cut/paste accelerators altoghether by removing them from main_menu.xrc, I can copy/paste again from the tools+ window with Ctrl+C,V.

[oBFusCATed]

This is the issue: http://trac.wxwidgets.org/ticket/11320
I've stopped following it after I've realised they don't care about the problem I've reported.
I think they broke the correct behaviour on windows, too, and made it the same as on linux

[dmoore]

This is the issue: http://trac.wxwidgets.org/ticket/11320
I've stopped following it after I've realised they don't care about the problem I've reported.
I think they broke the correct behaviour on windows, too, and made it the same as on linux

That seems like exactly OPs problem. (And something like this is clearly affecting Tools+ output window on wx2.8 & windows)

[BlueHazzard]

sry, i forget my os: windows7

This is the issue: http://trac.wxwidgets.org/ticket/11320
I've stopped following it after I've realised they don't care about the problem I've reported.
I think they broke the correct behaviour on windows, too, and made it the same as on linux

That seems like exactly OPs problem. (And something like this is clearly affecting Tools+ output window on wx2.8 & windows)

is this also related to the CC error?

[MortenMacFly]

IIRC we also updated the scintillla component to v3.3.2. I've seen in the changelogs to v3.3.3 that there was a bugfix related to copy issues on wxGTK. Maybe thats the reason - I am experiencing with v3.3.3 by now, but there was a(nother) API change that causes me headache becasue it affects important interfaces to wxScintilla.