Reason to update to 25.03?

[Mr.Madguy]

After using 25.03 for several days, I've found out, that it's just a little bit more laggy version of 20.03. Same annoying problems are still there. For example Ctrl+C/Ctrl+V bug, that has taught me bad behavior, I would carry to other programs - to copy things via right click, instead of just pressing Ctrl+C. And overall I didn't have any other problems with 20.03 except this one. So, may be it's reasonable to downgrade?

[stahta01]

Since, you give no link to good info on the problem; I think the problem will never be fixed.

Obvious info needed include; but, not limited to
OS Name and Version
wxWidgets version
How to duplicate the alleged problem

Tim S.

[dthu]

Ctrl+c and Ctrl+v work for me.

[Krice]

The previous version in Windows didn't have keybinds plugin so it was good reason to update, I could finally reassign F5 to build and run, and F9 to set breakpoint, as they are in Visual Studio. And Ctrl+F7 to compile current file. Another reason is that new version's gcc is 14. Changelog shows quite a lot of fixes, but I guess many of those are "invisible" to some users.

Startup in Windows 10 is much slower than it was before. In Linux exiting Code::Blocks was slow, but it became faster when I changed codecompletion to clangd-client. Funny that it's reversed: Windows has slow startup but fast exit and Linux (with codecompletion) has fast startup and slow exit. I don't know why it's slow in both cases, must be some serious stuff happening.

[Mr.Madguy]

Since, you give no link to good info on the problem; I think the problem will never be fixed.

Obvious info needed include; but, not limited to
OS Name and Version
wxWidgets version
How to duplicate the alleged problem

Tim S.

I thought it was well known problem. OS is Windows. wxWidgets is 3.2.7. Ctrl-C doesn't work most of the time, if it used to copy anything from one tab to another. Copying via right click works. Ctrl-V works.

[stahta01]

Since, you give no link to good info on the problem; I think the problem will never be fixed.

Obvious info needed include; but, not limited to
OS Name and Version
wxWidgets version
How to duplicate the alleged problem

Tim S.

I thought it was well known problem. OS is Windows. wxWidgets is 3.2.7. Ctrl-C doesn't work most of the time, if it used to copy anything from one tab to another. Copying via right click works. Ctrl-V works.

I did not see it under Windows 10; but I really do not use CNTL-C that often inside Code::Blocks; you do realize that a third-party app could be causing the problem, correct?

Tim S.

[stahta01]

Tried it 6 times under Windows 11 from one tab to another editor tab with both tabs saved to a file at the start of testing.
Edit: Both tabs also where part of the current CB project.

Tim S.

[Mr.Madguy]

Tried it 6 times under Windows 11 from one tab to another editor tab with both tabs saved to a file at the start of testing.
Edit: Both tabs also where part of the current CB project.

Tim S.

I have this problem in 90% cases. Sometimes it works. I'm not sure, why. In most cases it works for some time shortly after launching C::B. Then it stops. If I press Ctrl+C on one tab and try to Ctrl+V on another - previously copied code is pasted.

[stahta01]

Tried it 6 times under Windows 11 from one tab to another editor tab with both tabs saved to a file at the start of testing.
Edit: Both tabs also where part of the current CB project.

Tim S.

I have this problem in 90% cases. Sometimes it works. I'm not sure, why. In most cases it works for some time shortly after launching C::B. Then it stops. If I press Ctrl+C on one tab and try to Ctrl+V on another - previously copied code is pasted.

From the CB log these are the CB Plugins that were enabled under Win11 testing.
I copied 6 separate lines from tab 1 to tab 2 without issue. I would disable most of the CB Plugins to see if an CB Plugin is the cause.

Code

Loading:
Compiler
DevPakUpdater
ScriptedWizard
ToDoList
ToolsPlus

[Mr.Madguy]

Ok, I'll try to disable plugins, if I'll have time. I've already disabled 2 suspicious ones, that can affect clipboard. But please remember, that, again, I use default settings. I.e. if problem is caused by one of plugins - then it's devs' fault, that they enable it by default and provide unstable default environment to their users.

[stahta01]

Ok, I'll try to disable plugins, if I'll have time. I've already disabled 2 suspicious ones, that can affect clipboard. But please remember, that, again, I use default settings. I.e. if problem is caused by one of plugins - then it's devs' fault, that they enable it by default and provide unstable default environment to their users.

No, it is the fault of users who fail to report enough info to duplicate problems.
It is the responsibility of the CB Devs to fix problems that are reported with enough info to duplicate the problem.
Edit: I am not an CB Developer. I was in the past a regular CB user, who submitted patches and tried to duplicate reported problems.
Now days, I just try to build wxWidgets and Code::Blocks under MSys2 mingw64.

Tim S.

[Mr.Madguy]

No, it is the fault of users who fail to report enough info to duplicate problems.
It is the responsibility of the CB Devs to fix problems that are reported with enough info to duplicate the problem.
Edit: I am not an CB Developer. I was in the past a regular CB user, who submitted patches and tried to duplicate reported problems.
Now days, I just try to build wxWidgets and Code::Blocks under MSys2 mingw64.

Tim S.

Well, devs should test everything with default settings, right? Disabling 2 obvious plugins hasn't helped. Is there some of list of mandatory plugins, i.e. disabling them would affect CB's base functionality? I want to try to disable everything, except the most important ones.

[evilcoward]

I haven't yet installed 25.03, but can confirm problem with Ctrl+C on old version (OS is Win 7). Assuming behavior is the same, Ctrl+C is guaranteed to fail if your mouse cursor is over one of the tabs (and when you want to copy from one tab to another, it often is). It probably redirects all keyboard events to tab manager so that you can navigate with arrows, but it works horribly. Apart from Ctrl+C it is also annoying that it will not type any text if your cursor accidentally hovers over some tabs. And it doesn't even provide any convenience, since to navigate with arrows you still need to first hover your mouse over tabs but then you can just click tab with mouse.

[stahta01]

I haven't yet installed 25.03, but can confirm problem with Ctrl+C on old version (OS is Win 7). Assuming behavior is the same, Ctrl+C is guaranteed to fail if your mouse cursor is over one of the tabs (and when you want to copy from one tab to another, it often is). It probably redirects all keyboard events to tab manager so that you can navigate with arrows, but it works horribly. Apart from Ctrl+C it is also annoying that it will not type any text if your cursor accidentally hovers over some tabs. And it doesn't even provide any convenience, since to navigate with arrows you still need to first hover your mouse over tabs but then you can just click tab with mouse.

Much better description and you told the windows version number; good job reporting.
Edit: I was able to duplicate under Win10 and CB 25.03.

Tim S.

[Mr.Madguy]

I haven't yet installed 25.03, but can confirm problem with Ctrl+C on old version (OS is Win 7). Assuming behavior is the same, Ctrl+C is guaranteed to fail if your mouse cursor is over one of the tabs (and when you want to copy from one tab to another, it often is). It probably redirects all keyboard events to tab manager so that you can navigate with arrows, but it works horribly. Apart from Ctrl+C it is also annoying that it will not type any text if your cursor accidentally hovers over some tabs. And it doesn't even provide any convenience, since to navigate with arrows you still need to first hover your mouse over tabs but then you can just click tab with mouse.

I'm not sure, how it happens. My experience: longer I use CB after starting it - lesser chance of successful Ctrl+C. In most cases it works just after starting. But then it becomes worse and worse. For example just few hours ago I experimented with it a little bit. First I was able to copy things on the second attempt. But then it stopped working completely.

I thought, that being unable to type anything was somehow connected to auto-completion getting stuck sometimes. It feels like 25.03 is less prone to this problem.