Jacqueline, Craig, Terry,
Thank you very much for your answers.
Best,
Hery
On 04/27/2018 01:36 AM, J. Landman Gay via use-livecode wrote:
Or use a normal field as Craig suggested and create soft-wrapped lines
by inserting ASCII 11 at line breaks. These select as normal lines but
visually appe
Thank you very much Richmond.
Your answer was very helpful. :-)
Best,
Hery
On 04/27/2018 05:09 AM, Richmond via use-livecode wrote:
I've just set up a stack containing 2 fields; one called "fff"
containing your
original string, another called "fCHOPPED" that is a scrolling list
field.
I h
Well that chopping up doesn't have to take place between fields: it
could, say, start with
the string in a string-variable, and the chopped-up bits end up in a
2-dimensional array.
Richmond.
On 27/4/2018 5:47 pm, Bob Sneidar via use-livecode wrote:
On a mobile device??
Bob S
On Apr 27, 20
On a mobile device??
Bob S
> On Apr 27, 2018, at 02:09 , Richmond via use-livecode
> wrote:
>
> I've just set up a stack containing 2 fields; one called "fff" containing your
>
> original string, another called "fCHOPPED" that is a scrolling list field.
>
> I have a button containing this s
I've just set up a stack containing 2 fields; one called "fff"
containing your
original string, another called "fCHOPPED" that is a scrolling list field.
I have a button containing this script:
on mouseUp
put fld "fff" into FFF
set the itemDelimiter to ","
put 1 into KOUNT
repeat u
Or use a normal field as Craig suggested and create soft-wrapped lines by
inserting ASCII 11 at line breaks. These select as normal lines but
visually appear as separate lines.
From the 5.5 release notes:
The engine will now interpret a numToChar(11) character in a field
paragraph as an expli
Or perhaps use a form type datagrid - which will allow you to present and
select multi-lined option more readily.
Regards,
Terry...
On 27/04/2018 2:33 pm, "use-livecode on behalf of dunbarx via use-livecode"
wrote:
Hi.
If I were you, with the task you laid out, I would not use
Hi.
If I were you, with the task you laid out, I would not use an option menu.
It is not good with wide menuItems, and it is not natural, if even possible,
to select multiple lines in the way you want.
Use a list field instead. A field has many properties that are denied an
optionMenu, which is r
Dear Livecode programmers,
I need you good expertise again.
I'm development an small app for a French insurance company.
I have an option menu button.
Some elements in this option menu are very large. Example:
/Dialyse rénale, insuffisance rénale, maladie rénaleDID, diabète de type
1//,//diabè
