Skip to content
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

Open
J-Dunn opened this issue Nov 11, 2015 · 6 comments
Open

debugger 'command line arguments' broken #305

J-Dunn opened this issue Nov 11, 2015 · 6 comments

Comments

@J-Dunn
Copy link

J-Dunn commented Nov 11, 2015

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.

@J-Dunn
Copy link
Author

J-Dunn commented Nov 11, 2015

Seems the relevant code is here:
debugger/src/tpage.c

/* arguments */
    args_frame = gtk_frame_new(_("Command Line Arguments"));
    hbox = gtk_hbox_new(FALSE, 0);
    gtk_container_set_border_width(GTK_CONTAINER(hbox), 5);
    args_textview = gtk_text_view_new ();
    gtk_text_view_set_wrap_mode(GTK_TEXT_VIEW(args_textview), GTK_WRAP_CHAR);
    buffer = gtk_text_view_get_buffer(GTK_TEXT_VIEW(args_textview));
    g_signal_connect(G_OBJECT(buffer), "changed", G_CALLBACK (on_arguments_changed), NULL);
    gtk_container_add(GTK_CONTAINER(hbox), args_textview);
    gtk_container_add(GTK_CONTAINER(args_frame), hbox);

I'm only getting the frame !

@J-Dunn
Copy link
Author

J-Dunn commented Nov 11, 2015

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?

@J-Dunn
Copy link
Author

J-Dunn commented Nov 13, 2015

https://developer.gnome.org/gtk2/stable/GtkBox.html#gtk-box-pack-start

fill
TRUE if space given to child by the expand option is actually allocated to child , rather than just padding it. This parameter has no effect if expand is set to FALSE. A child is always allocated the full height of a GtkHBox and the full width of a GtkVBox. This option affects the other dimension

That does not seem to be happening to the hbox containing the textedit in question !

@Yanpas
Copy link

Yanpas commented Nov 15, 2015

Confirm, I can enter agruments, but when I run it - nothing happens
_2015-11-15_15-23-44
_2015-11-15_15-23-57

@Yanpas
Copy link

Yanpas commented Jan 14, 2016

Seems like my problem differs... I'll open new report

@b4n
Copy link
Member

b4n commented Feb 8, 2016

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants