-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
debugger 'command line arguments' broken #305
Comments
Seems the relevant code is here:
I'm only getting the frame ! |
LOL, these dumb "widgets" can shrink down so small that they no longer display their contents. By coincidence, my F4 window was just the right size to have the frame display cleanly but to hide text element that it contains and without displaying a visible cursor. So all I had was the inactive frame I reported. Having a lib of automatically resizing widgets is nice: as long as they resize in an intelligent and readable fashion. In fact this window turns into a complete mess if it gets resized even smaller. Is there a property to set a minimum height for these elements so that they don't start to overly on top of each other , dribble onto the status bar or loose their primary functionality , like text input? |
https://developer.gnome.org/gtk2/stable/GtkBox.html#gtk-box-pack-start fill That does not seem to be happening to the hbox containing the textedit in question ! |
Seems like my problem differs... I'll open new report |
@J-Dunn the problem is that Geany's bottom pane, where the debugger tab is located, is set to allow shrinking smaller than what the widgets in it need. You then see the effects of under-allocation. In Geany this was done on purpose so you can hide the bottom panel completely, or make it as small as you like no matter what. I'm not sure what the debugger plugin can do here, but maybe try and resize the bottom pane to a more sensible size when it loads or something, so it is initially in an usable state. |
Building debugger from git I find that in the debug tab of the message window (F4) there is an empty frame with the title 'command line arguments' . It appears that this should be and editable input.
There is no way to enter command line arguments for the debugger.
The text was updated successfully, but these errors were encountered: