From: Sam Ravnborg <sam@ravnborg.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Petr Baudis <pasky@suse.cz>
Subject: Re: [PATCH/RFC] kconfig/lxdialog: make lxdialof a built-in
Date: Fri, 28 Jul 2006 16:59:47 +0200 [thread overview]
Message-ID: <20060728145947.GA29095@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0607281348420.6761@scrub.home>
On Fri, Jul 28, 2006 at 04:09:03PM +0200, Roman Zippel wrote:
> Hi,
>
> On Thu, 27 Jul 2006, Sam Ravnborg wrote:
>
> > Dedided to take another stamp on an old TODO item of making lxdialog
> > a built-in. Following patch is first step to do so.
> > The patch makes it a built-in - but with two open issues that I yet
> > have to address.
>
> Looks good. :)
> There is a NULL pointer problem with empty menus, item_cur is NULL and a
> select or exit will cause a segfault in item_set_selected().
Fixed. Introduced a dummy variable "item_nil" that item_cur points to in
the empty case. So no need for special cases all over.
>
> > I will during the weekend try to address the resize issue.
>
> Wasn't it working at some point?
> Anyway, it doesn't has to be overly complex either, e.g. if you delay it
> to the next key event, it's fine too. The signal handler would just set a
> flag and when wgetch returns, the display is reinitialized.
My experiments so far tells me that a resize generates KEY_RESIZE so it
is a simple matter of handling KEY_RESIZE correct in the different
dialog_* functions - and no signal handler needed. Thats looks like the
approach taken in the dialog package too.
>
> > The double ESC ESC thing I dunno how to fix.
>
> I think the easiest would be to just ignore the first ESC, it matches the
> documented behaviour and e.g. mc has the same behaviour. The delay of the
> single ESC makes it a bit annoying/confusing to use, so that sticking to
> the double ESC is IMO safer.
> I played with it a little and below is an example, which implements this
> behaviour for the menu window.
Thanks - will implment this for all the dialog_* functions.
Sam
next prev parent reply other threads:[~2006-07-28 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 20:27 Sam Ravnborg
2006-07-28 14:09 ` Roman Zippel
2006-07-28 14:59 ` Sam Ravnborg [this message]
2006-07-30 12:42 ` Denis Vlasenko
2006-07-30 21:44 ` Sam Ravnborg
2006-07-30 22:19 ` Roman Zippel
2006-07-29 20:53 ` Sam Ravnborg
2006-07-29 20:56 ` Sam Ravnborg
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=20060728145947.GA29095@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=zippel@linux-m68k.org \
/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
Powered by JetHome