User forums > General (but related to Code::Blocks)
Reason to update to 25.03?
stahta01:
--- Quote from: Mr.Madguy on April 09, 2025, 09:54:26 pm ---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.
--- End quote ---
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:
--- Quote from: stahta01 on April 10, 2025, 12:10:28 am ---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.
--- End quote ---
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:
--- Quote from: evilcoward on April 10, 2025, 09:38:19 pm ---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.
--- End quote ---
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:
--- Quote from: evilcoward on April 10, 2025, 09:38:19 pm ---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.
--- End quote ---
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.
Navigation
[0] Message Index
[*] Previous page
Go to full version