#1603 CallStack Debug Window default size issue

[Tiger Beard]

Problem: An opened CallStack debug window is too small to show anything useful. Mouse action required each time, because it does not remember any changes.

Tested in Linux, build 13845 (close to head at this time). The problem exists for a very long time (years)

How to reproduce.

• Ensure debug view has MemoryDump and CallStack windows docked right hand side. Close both windows.
• Start a program in Debug. CB switchtes to Debug view. Both debug windows are not visible.
• Select ToolbarIcon DebugWindow/MemoryDump. A docked window opens. Note window width.
• Close MemoryDump again
• Now DebugWindow/CallStack. A docked window opens. Note different width to Memory window. Note that no function names are visible, just addresses and numbering. Resize until you can read function call order.
• Close CallStack and directyl open it again. Observe that I had its last size for a fraction of a second and then jumps back to its (too small) default size. Resize my mouse again to see function call order.
• Repeat last step as desired

Generally all debug windows do not persist size consistently. But its worst for the CallStack, because its default is really unusable. Others, e.g the MemoryDump window have a good default size. Also in 20+ years using CB I never found a reason why I would want to see "Nr" and "Address" columns. imho best

Possible Solutions

• all DebugWindows remember their last size
  or
• CallStack remembers its size
  or
• CallStack table columns remembers their size/they can be enabled/disabled
  or
• Callstack window default size is increased such that "Function" column is visible

PS: Ino: why I open/close CallStack very often:

• Debugging perfromance is slowed down noticeably (even on modern 16 core cpu!), at least with large projects
• Linux/gdb: CB bug that CallStack does not update on halt before first breakpoint. It does update after close/re-open. Typical use case: find out where crash happened
• takes valuable screen estate

[Miguel Gimenez]

Works fine on Windows. Are you using Wayland?

If yes, can you try at least [r13848] or start C::B from console using "GDK_BACKEND=x11 codeblocks"?

[Tiger Beard]

Wouldn't have thought this is Liunx specific.

No, I my distro is non-wayland, can't be that.

[Miguel Gimenez]

I have rechecked on Windows and it also fails.

[Tiger Beard]

Thats actually good news for AUI.

[Tiger Beard]

PS: I must admit that this issue is disturbing my workflow for years, currently many times a day. But not bad enough put another ticket on the pile.

Since I guessed you might have a look at it, just the prosepect of a chance for an improvement, is great. Whatever change you may come up with it will make the flow much nicer.

A bit like the ThreadSearch a few years ago where you simplified an idea to just re-start the last search on an empty text field. Simple change, great impact. Every time I use that its with a smile remembering that.