Trying to use the Segmented Control

Richmond richmondmathewson at
Sun Dec 6 05:16:07 EST 2020

When I was about 18 I was driving tractors on a farm: really 
old-fashioned things with about 3 gears.

Later, in the United States, I learnt to drive a car; out car was a Ford 
Tempo with 5 gears and a reverse.

However, when I went to take the test the officers there would not let 
me use our car because it had a pea-sized spot of the windscreen. So, I 
borrowed a friend's car: the only problem was that it was an automatic: 
so I took a driving test in an automatic
car when I had never driven one before . . . what a load of rubbish.

I, then, left the U.S. and did not drive a car for about 6 months, and 
managed to have my American licence stolen.

I started driving again in the United Arab Emirates on the basis of a 
Saudi licence I had got for a bottle
of fake Chanel number 5.

That's when I really started to drive.

The few times I have had to drive a car with an automatic gear system 
since then I have generally panicked as
they make me feel out of control.

WIDGETS seem to me like cars with automatic transmission: all very 
clever, drive themselves, but no chance for
any creative driving.

Personally I'll always opt for 'stick' given the choice.

On 30.11.20 13:05, R.H. via use-livecode wrote:
> Basically, I think, it is a nice widget.
> --- But sometimes, I would like to show text with icons together, or each
> icon in a different color. Possible?
> --- Then I would like to import whatever icon or image and individually set
> its size, and margins individually. I like to have access to the details of
> each segment and it's look and feel. Even each segment's rect and other
> details should be modifiable. I would like to be able to define the size
> and the color of each object's border and dividing lines. The only way
> around is scripting lines or whatever to be used as an overlay -- which is
> a kludge. But is it possible using LCB to address individual parts and
> define a more detail-grained API?
> --- Messages: I do not understand why not standard mouse messages would
> work here and are not supported.  Other messages than just "hilitedChange"
> should be detected. But it would be important, in my opinion, to allow each
> and every graphical widget to detect mouseWithin, mouseMove, mouseDown,
> mouseUp, mouseEnter, mouseLeave, etc.
> Is there anybody working on such widgets and updating them to newer
> versions? Is there a version history for each widget?
> The documentary of the widget (widgets) in the Dictionary could be enhanced
> with a first date of appearance and dates of new versions as well as
> enhancement requests or planned enhancements? I assume the author is
> LiveCode Ltd.?
> Roland
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the use-livecode mailing list