#1001 [CB 20.03 Bug Report] Not adding parentheses after function name auto completion

[Helder Batalha]

Dear all,
I've been using CB for 2 years now and I started it out in version 16.01 and I am still using this version because I don't like how version 17.12 looks and feels. But version 20.03 came out and went to check it out and I loved it.

However, the first thing I noticed when using it was that it is not adding parentheses after function name in auto completion and it is kind of a deal breaker. I am going to the settings toggling that option but nothing is changing. Even though it might not seem like a big deal but not having this feature is very annoying. I am not sure if this is a bug or it is one the changes in this new version.

Also selecting a few lines of code and want to put inside brackets or parentheses by just clicking the bracket or parentheses key is not working anymore. I think this is not a bug but I love that feature and was wondering if there is another way to accomplish this in.
However I made some tests and apparently this feature can be used in the CB 20.03, I openned the CB 20.03 having its default.conf file the same as the one I use in CB 16.01 and it worked but as soon as I deleted it and made CB 20.03 create its own default.conf file, the feature stopped working, and instead of embracing the selected blocked code when clicking one of these keys (, ), {, }, [, ], <, >, it just replaces it.

OS: Windows 10 64 bit
CB Release: Release 20.03 rev 11983 (2020-03-12 18:24:30) gcc 8.1.0 Windows/unicode - 64 bit

Some help please!!

[Helder Batalha]

Only an update:

I deleted the whole 'codeblocks-code-r12201-trunk' folder and unzipped it again and started the building steps from the very beginning, I followed every step I described above and this time it built succefully. I am running codeblocks and 'not adding parentheses' issue is solved.

Thank you very much.

[Teodor Petrov]

@Miguel Gimenez (related to the patch)

Good, but is this thing broken in the stc sample? x2
(probably you'll have to modify it to test it)

I'm asking this because when we port the new popups from wx we don't want to re-introduce this bug one more time. And as far as I can see this is a windows only thing, because I can't reproduce the problem and I'm on relatively recent wx-master.

[bluehazzard]

I tried to reproduce this with the stc sample, but i was not able to use the wxEVT_COMMAND_LIST_ITEM_SELECTED event, also not with the patch from miguel...

But with the newest version of STC in wxWidgets, there is the wxEVT_STC_AUTOCOMP_SELECTION_CHANGE event, that works,

so i think we can use this patch, and have then to upgrade to the new event...

[bluehazzard]

@fuscated can you check if this patch has any side effects on linux? If not i will comit this, because it is annoying as hell on windows....

[Miguel Gimenez]

You can write it this way:

/* C::B begin */
#ifdef __WXMSW__
        SetExtraStyle(GetExtraStyle() & ~wxWS_EX_BLOCK_EVENTS);
#endif
/* C::B end */

[Teodor Petrov]

@bluehazzard: No intention to do any work on this at the moment. If I'll work on this I'll port the whole change made in wx. Make sure to mark it with the cb tags and add a comment, so it is not lost the next time I do syncs. There is also macOS you have to test, so the easy thing is to make it for windows only. :)

[bluehazzard]

Fixed in [r12207]
thank you for your contribution