Re: [code] [textadept] ui.dialogs

From: Mitchell <>
Date: Wed, 15 Jan 2014 14:53:27 -0500 (Eastern Standard Time)

Hi Richard,

On Wed, 15 Jan 2014, Richard Philips wrote:

> Hello Mitchell,
> I missed this mail but I replied to a later mail from Robert about this.
>> Would a textbox work for you? You could parse by line. I know it's not
>> ideal, but it might be less error-prone and more intuitive.
> An (editable) textbox is what I use now!

I'm sorry I misunderstood your original e-mail. Your response to Robert
clarified your method. I somehow got the idea you were parsing fields from
a one-line inputbox...

> [snip]
>> Yes this is not trivial to implement. It also begs some questions.
>> Should there be labels next to each inputbox? If so, how should the
>> API declare them? How should it return the values from all inputboxes?
> A suggestion for the API:
> ui.dialogs.inputbox
> - if option |informative_text is 'not a table' (string), keep the
> current functionality
> - if option informative_text is a table, present a multiline
> functionality
> (if it is a table, the option text should be a table as well)
> return selected button or exit code, table with the input text

Thanks. That's something for me to think about.


You are subscribed to
To change subscription settings, send an e-mail to
To unsubscribe, send an e-mail to
Received on Wed 15 Jan 2014 - 14:53:27 EST

This archive was generated by hypermail 2.2.0 : Thu 16 Jan 2014 - 06:26:48 EST