Svg Icon Tool
Mike Kerner
MikeKerner at roadrunner.com
Fri Aug 26 10:34:24 EDT 2022
i could see, for someone who wants it to behave the way it behaves now,
that retaining the current behavior and adding to it would be better.
the control can work both ways, a manual mode and an automagical mode.
On Fri, Aug 26, 2022 at 10:28 AM Mike Kerner <MikeKerner at roadrunner.com>
wrote:
> correct, the hiliteChanged message is superfluous in this scenario, and
> the developer would just manage the touch/mouse messages
> i disagree that flipping the hilite to one and then back is better. the
> hilite is an indicator of state. if the state is not allowed to change,
> then the hilite should not change.
> in the current operation, the user hits a selection. the hilite changes.
> at this point, there aren't any good options. if we switch cards, then do
> the test, tell the user that the selection is not allowed, then switch
> back, they get this jerky transition, and we have to restore the previous
> state. if we do not make the transition, then they get the hilite changing,
> then they get rejected, and then we have to switch the hilite back to what
> it was, before.
>
> On Fri, Aug 26, 2022 at 10:14 AM Brian Milby via use-livecode <
> use-livecode at lists.runrev.com> wrote:
>
>> Ok, then we need a full spec on how this would work. It is not just the
>> addition of a message.
>>
>> To get what you are desiring, it would be most consistent to just add the
>> mouse messages and the autoHilite property.
>>
>> I would still want the silent option since that works most in the grain
>> of the current functionality.
>>
>> In your use case, you wouldn’t even use the hiliteChanged message. You
>> would just act based on the mouseUp after your checks.
>>
>> From a UI perspective, I think it makes more sense for the object to
>> highlight on the touch and then revert on the mouseUp if not permitted.
>>
>> > On Aug 26, 2022, at 9:28 AM, Mike Kerner via use-livecode <
>> use-livecode at lists.runrev.com> wrote:
>> >
>> > you would have a property for autohilite, and if that is false, the
>> > developer would be responsible for setting the hilite. that's the way
>> it's
>> > implemented with other controls.
>> >
>> >> On Fri, Aug 26, 2022 at 9:23 AM Brian Milby via use-livecode <
>> >> use-livecode at lists.runrev.com> wrote:
>> >>
>> >> The silent update would allow that to happen in the hilitechanged
>> handler.
>> >>
>> >> I don’t know how you would implement a pre… message. How would the
>> widget
>> >> know whether to proceed or not? The two messages would fire almost
>> >> simultaneously. There also isn’t any way to tell the widget to cancel
>> the
>> >> highlight action, which would be needed.
>> >>
>> >> A mouseDown message may work but would still need a way to cancel the
>> >> highlight. I think the silent change is the most seamless way to
>> >> accomplish this task.
>> >>
>> >> In general I think that normal mouse messages should be passed from
>> >> widgets - even if they add specialized functionality with additional
>> >> messages. I don’t think they would solve this issue on their own
>> though.
>> >>
>> >> (I also did some work in this widget to add the nothing and multiple
>> >> selections)
>> >>
>> >>
>> >>
>> >>> On Aug 26, 2022, at 9:03 AM, Mike Kerner via use-livecode <
>> >> use-livecode at lists.runrev.com> wrote:
>> >>>
>> >>> i don't think so. i want to be able to be able to intercept the
>> >>> touch/click, and decide what to do. sometimes i want to ignore it.
>> >>> sometimes i want to throw up an error and not switch. sometimes i
>> want to
>> >>> do something else, first.
>> >>>
>> >>>> On Thu, Aug 25, 2022 at 5:48 PM Brian Milby via use-livecode <
>> >>>> use-livecode at lists.runrev.com> wrote:
>> >>>>
>> >>>>
>> >>>> I think what we probably need is simply:
>> >>>>
>> >>>> set the hilitedItemSilently of widget 1 to 1
>> >>>> Or
>> >>>> set the hilitedItemWithoutMessage of widget 1 to 1
>> >>>>
>> >>>> This would allow more elegant solutions to many of the raised issues.
>> >>>>
>> >>>> Thanks,
>> >>>> Brian
>> >>>>
>> >>>>
>> >>>> Sent from my iPhone
>> >>>>
>> >>>>> On Aug 25, 2022, at 2:48 PM, Mike Kerner via use-livecode <
>> >>>> use-livecode at lists.runrev.com> wrote:
>> >>>>>
>> >>>>> the two things that are glaring, imho are
>> >>>>> * [preHiliteChanged](
>> >> https://quality.livecode.com/show_bug.cgi?id=23207)
>> >>>> -
>> >>>>> someone taps on a selection. i do a check, throw up a "nope", and
>> >> nothing
>> >>>>> changes. this one is preventing me from moving off of the tmControls
>> >>>> navbar.
>> >>>>> * autowidth to the card width.
>> >>>>> but there are several others, as well
>> >>>>>
>> >>>>
>> >>
>> https://quality.livecode.com/buglist.cgi?quicksearch=navigation%20bar&list_id=105904
>> >>>>> listen, i get it. i need to re-learn lcb and actually use it.
>> >>>>> but i also have force powers, so i know that someone is going to do
>> >> these
>> >>>>> things, before i do, and then i won't have to.
>> >>>>>
>> >>>>>> On Thu, Aug 25, 2022 at 2:39 PM Ralph DiMola via use-livecode <
>> >>>>>> use-livecode at lists.runrev.com> wrote:
>> >>>>>>
>> >>>>>> Mike,
>> >>>>>> I have used my own version of the navbar widget for years. I added
>> an
>> >>>>>> option to enlarge/vertically justify the icon if there is no label
>> and
>> >>>>>> eliminated the "new item" thingy. I think the stock widget already
>> >> lets
>> >>>> you
>> >>>>>> select the zero option. I added that back before the stock widget
>> let
>> >>>> you
>> >>>>>> do it. What changes/enhancements are you looking for?
>> >>>>>>
>> >>>>>> I also have LCS routines to store the navbar options as a custom
>> >>>> property
>> >>>>>> array. I have handlers to add/delete/change option text and icons
>> via
>> >>>>>> script for a contextual UI. They are not documented or polished
>> but if
>> >>>>>> there is any interest I will look into it.
>> >>>>>>
>> >>>>>> Ralph DiMola
>> >>>>>> IT Director
>> >>>>>> Evergreen Information Services
>> >>>>>> rdimola at evergreeninfo.net
>> >>>>>>
>> >>>> _______________________________________________
>> >>>> use-livecode mailing list
>> >>>> use-livecode at lists.runrev.com
>> >>>> Please visit this url to subscribe, unsubscribe and manage your
>> >>>> subscription preferences:
>> >>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> On the first day, God created the heavens and the Earth
>> >>> On the second day, God created the oceans.
>> >>> On the third day, God put the animals on hold for a few hours,
>> >>> and did a little diving.
>> >>> And God said, "This is good."
>> >>> _______________________________________________
>> >>> use-livecode mailing list
>> >>> use-livecode at lists.runrev.com
>> >>> Please visit this url to subscribe, unsubscribe and manage your
>> >> subscription preferences:
>> >>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> >>
>> >> _______________________________________________
>> >> use-livecode mailing list
>> >> use-livecode at lists.runrev.com
>> >> Please visit this url to subscribe, unsubscribe and manage your
>> >> subscription preferences:
>> >> http://lists.runrev.com/mailman/listinfo/use-livecode
>> >>
>> >
>> >
>> > --
>> > On the first day, God created the heavens and the Earth
>> > On the second day, God created the oceans.
>> > On the third day, God put the animals on hold for a few hours,
>> > and did a little diving.
>> > And God said, "This is good."
>> > _______________________________________________
>> > use-livecode mailing list
>> > use-livecode at lists.runrev.com
>> > Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> > http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>
>
> --
> On the first day, God created the heavens and the Earth
> On the second day, God created the oceans.
> On the third day, God put the animals on hold for a few hours,
> and did a little diving.
> And God said, "This is good."
>
--
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
and did a little diving.
And God said, "This is good."
More information about the use-livecode
mailing list