Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Keybinder v2 notes/problems

<< < (4/15) > >>

Pecan:

--- Quote from: oBFusCATed on December 14, 2019, 03:11:50 pm ---Another problem I've discovered is that a v2 file saved with wx28 build doesn't work on wx313 build on linux. I've tried relatively recent build. Please let me know if you need more details.

--- End quote ---

I cannot duplicate this error on Windows; nor on Linux Mint19 using wxWidgets 3.1.3 .

I suspect your .config/codeblocks directory already contains a [personality].cbKeybinder20.conf file.
In which case neither [personality].cbKeybinder10.ini nor ancient cbKeybinder10.ini will be scanned for key definitions.
 

oBFusCATed:
Yes, I'm migrating from v2 to v2, but for some reason the file generated by v2.wx28 doesn't work correctly with v2.wx31.
I've custom keybindings - ctrl-shift-f for view -> focus thread search is an example.

Pecan:

--- Quote from: oBFusCATed on December 19, 2019, 09:43:06 am ---Yes, I'm migrating from v2 to v2, but for some reason the file generated by v2.wx28 doesn't work correctly with v2.wx31.
I've custom keybindings - ctrl-shift-f for view -> focus thread search is an example.

--- End quote ---

I cannot test this since ThreadSearch will not run with head.
I get asserts when CB loads ThreadSearch.

Why would anybody be building head with wx28. I thought we were dropping wx28.

Do you mean that you are attempting to use  (copy)[profile].cbKeyBinder20.conf build by wx28 on CodeBlocks built by wx31?

oBFusCATed:
I have a centos7 build which is wx28. This is my regular build I use every day. It is not the latest version, but it is pretty new.
I want to migrate to wx3.x and I'm experimenting with a centos7 build which is using wx3.1.3.
This means that I was using wx28 for some time, then I've installed the new build which is now wx3.1.3 and I've discovered this breakage.

Pecan:

--- Quote from: oBFusCATed on December 19, 2019, 08:33:56 pm ---I have a centos7 build which is wx28. This is my regular build I use every day. It is not the latest version, but it is pretty new.
I want to migrate to wx3.x and I'm experimenting with a centos7 build which is using wx3.1.3.
This means that I was using wx28 for some time, then I've installed the new build which is now wx3.1.3 and I've discovered this breakage.

--- End quote ---

@oBFusCATed

I'm having trouble creating this situation. I must be mis-understanding.

Could you give me the exact steps to cause this problem, starting with:

* 1 ) the orginal Codeblocks SVNversion# + wxVersion that created the original keybinder file.
* 2) The new Codeblocks SVNversion# + wxVersion that you are now using that does not correctly translate the keybinder file made by #1 above.
* 3) can you attach the original keybinder file that is causing the problem

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version