Weird tabs behavior

[just_some_random_name]

Hello,
I have issues with tabs behaviour in codeblocks (called notebooks I guess?).

The first issue is more of an annoyance, but I'll try my luck:
Whenever I close current tab it will skip over different tab to eventually skip to previously opened tab, see gif:



The second issue:
Whenever I close not-currently-opened tab, my current tab is switched to some random one:


This is especially annoying when I'm closing a lot of tabs and it just keep switching to random files.

Can it be configured somehow? Or is it bug?

Thanks!

[oBFusCATed]

OS/C::B versions?

[just_some_random_name]

Ah sorry, I cropped it from the gifs;
OS: 18.04 kubuntu
C::B: 17.12

[oBFusCATed]

And what is your wxGTK version? (Execute wx-config --list and paste the results from it)

[just_some_random_name]

$ wx-config --list

   

Code Select Expand

Default config is gtk2-unicode-3.0

  Default config will be used for output

  Alternate matches:
    base-unicode-3.0


[oBFusCATed]

OK, I can reproduce this on Ubuntu 18.04, but not on my gentoo. Strange. Both are using wxgtk 3.0.4 + gtk2...

[oBFusCATed]

In theory:
1. when you close a selected tab, the one before it should be selected
2. when you close non selected tab, the selected one should not change.

Currently on ubuntu the behaviour is strange...

[just_some_random_name]

Thanks for trying out. If you have any suggestion for me to try, go ahead, I'll gladly help

[oBFusCATed]

This behaviour is caused by the BrowseTracker plugin. If you don't use it you can disable it and it should stop doing it.

[just_some_random_name]

oooh yes, it feels so good to painlessly close tabs again.

Few observations:
When I tried to disable the plugin for the first time, several assertions were thrown, that caused CB to be unresponsive. Unfortunately, I haven't noted them.

After a restart of CB, the plugin was disabled and tabs could be closed without issue (yay).

Again I tried to enable the plugin (no problem), and tabs were still closing without the issue.

Next, I restarted CB, the plugin was enabled and issue with tabs was present again. However, this time disabling the plugin was without assertion errors and issue with tabs disappeared again.

So TL;DR
If you want to use BrowseTracker plugin, disable and enable it on every start of codeblocks. Otherwise, keep it disabled.

[oBFusCATed]

@pecan Would it be possible to look at these?

[Pecan]

@pecan Would it be possible to look at these?

Yes, I'll explore it.