public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] TUI resize unification
Date: Thu, 15 Aug 2019 19:38:00 -0000	[thread overview]
Message-ID: <4d73b055-500f-e6e2-25b9-19db01efcc8b@redhat.com> (raw)
In-Reply-To: <20190815192244.17786-1-tom@tromey.com>

On 8/15/19 8:22 PM, Tom Tromey wrote:
> The TUI currently has two different ways to resize a window: the
> resize method, and the methods make_invisible_and_set_new_height and
> make_visible_with_new_height.
> 
> There's no deep reason to have two different ways to resize a window,
> so this patch unifies them, leaving just the "resize" method.
> 
> This also changes the locator to be handled more like an ordinary
> window and less like an adjunct of the associated source window.
> 
> gdb/ChangeLog
> 2019-08-15  Tom Tromey  <tom@tromey.com>
> 
> 	* tui/tui-io.c (tui_puts_internal): Check TUI_CMD_WIN before
> 	calling update_cmdwin_start_line.
> 	* tui/tui-winsource.h (struct tui_source_window_base)
> 	<do_make_visible_with_new_height, set_new_height>: Don't declare.
> 	<rerender>: Declare.
> 	* tui/tui-winsource.c (tui_source_window_base::update_tab_width):
> 	Call rerender.
> 	(tui_source_window_base::set_new_height): Remove.
> 	(tui_source_window_base::rerender): Rename from
> 	do_make_visible_with_new_height.
> 	* tui/tui-win.c (tui_resize_all, tui_adjust_win_heights): Use
> 	resize method.
> 	(tui_win_info::make_invisible_and_set_new_height)
> 	(tui_win_info::make_visible_with_new_height): Remove.
> 	* tui/tui-stack.h (struct tui_locator_window) <rerender>:
> 	Declare.
> 	* tui/tui-stack.c (tui_locator_window::rerender): New method.
> 	* tui/tui-regs.h (struct tui_data_window) <set_new_height,
> 	do_make_visible_with_new_height>: Don't declare.
> 	<rerender>: Declare.
> 	* tui/tui-regs.c (tui_data_window::rerender): Rename from
> 	set_new_height.
> 	(tui_data_window::do_make_visible_with_new_height): Remove.
> 	* tui/tui-layout.c (show_source_disasm_command, show_data): Don't
> 	call tui_show_locator_content.
> 	(tui_gen_win_info::resize): Call rerender.
> 	(show_source_or_disasm_and_command): Don't call
> 	tui_show_locator_content.
> 	* tui/tui-data.h (struct tui_gen_win_info) <rerender>: New
> 	method.
> 	(struct tui_win_info) <rerender>: Declare.
> 	<set_new_height, make_invisible_and_set_new_height,
> 	make_visible_with_new_height>: Don't declare.
> 	* tui/tui-data.c (tui_win_list::rerender): New method.
> 	* tui/tui-command.h (struct tui_cmd_window)
> 	<do_make_visible_with_new_height>: Don't declare.
> 	* tui/tui-command.c
> 	(tui_cmd_window::do_make_visible_with_new_height): Remove.
> 
> gdb/testsuite/ChangeLog
> 2019-08-15  Tom Tromey  <tom@tromey.com>
> 
> 	* gdb.tui/empty.exp: Enable resizing tests.

Looks good to me.

Thanks,
Pedro Alves

  reply	other threads:[~2019-08-15 19:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15 19:22 Tom Tromey
2019-08-15 19:38 ` Pedro Alves [this message]
2019-08-18 23:00 ` New FAILs on gdb.tui/empty.exp (was: Re: [PATCH] TUI resize unification) Sergio Durigan Junior
2019-08-19 13:49   ` New FAILs on gdb.tui/empty.exp Sergio Durigan Junior
2019-08-20 18:58     ` Tom Tromey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4d73b055-500f-e6e2-25b9-19db01efcc8b@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).