What about the use of mobile-only commands… needing to always wrap them in
something to keep the IDE from touching.
if "mobile" is in the environment then
mobileControlSet tObject, tProp, tValue
> On Aug 10, 2017, at 6:50 PM, Monte Goulding via use-livecode
> <firstname.lastname@example.org> wrote:
>> On 11 Aug 2017, at 11:45 am, Mark Wieder via use-livecode
>> <email@example.com> wrote:
>> You know, if you'd post what you're trying to do it might be more possible
>> to stay on target here. For instance, I regularly have to fill an array with
>> constants in an initialization routine or use a custom property array filled
>> with constants. Is that any help? Or are you looking to make a macro
>> processor? Or a library of common <things>? Or something else?
> A library of common <things> is probably the best description at the moment
> but the use case is not reusable handlers as we have other means for that.
> Basically anything where you follow a common pattern to do a thing but you
> can’t abstract away so you don’t have to write the pattern any more.
> use-livecode mailing list
> Please visit this url to subscribe, unsubscribe and manage your subscription
use-livecode mailing list
Please visit this url to subscribe, unsubscribe and manage your subscription