Three very simple questions

Graham Samuel livfoss at
Tue Apr 28 15:43:26 EDT 2020

Bill, I think you’re right about the Guide not being searchable. I was going to point it out myself, but I began to think that I had used up my grumbling allowance, or at least I had not much left and needed to use it for other things.

Of course the Giude should be searchable!


Re grumbling - I have always been delighted by the way people on this list come to each other’s aid. This ‘invisible college’ is a really essential part of the LiveCode experience, I believe. I hope I say ‘thank you’ enough.

> On 26 Apr 2020, at 23:52, prothero--- via use-livecode <use-livecode at> wrote:
> Folks:
> I think Graham is doing LiveCode a favor by pointing out some of the ways a newby (even though he isn’t) might get messed up when learning LiveCode. We all get used to various approaches and newbies (even tho Graham isn’t) alert us to impediments for that very vital population of potential or new users.
> One thing that has bugged me is that when I click on the dictionary, I get a nice display of commands, etc, searchable. But when I click on the “Guide” tab, I get what looks like a very informative document. However, if I’m looking for a particular task and want to do a search, there is none. So, it seems to me like a very valuable newby document is crippled by the omission of a very basic feature.
> Or have I just missed something?
> Best,
> Bill
> William A. Prothero
> Santa Barbara, CA. 93105
>> On Apr 26, 2020, at 12:23 PM, Mark Wieder via use-livecode <use-livecode at> wrote:
>> On 4/26/20 12:09 PM, Sannyasin Brahmanathaswami via use-livecode wrote:
>>> "globals are evil"
>>> But we use  one array
>>> Global gConfigA
>>> and we stuff it with all manner of "things" including another arrays
>>> it turns about to quite useful
>> Yes, I do what you and Jacque do as a workaround, of course. I recently implemented a feature management infrastructure the same way, given the lack of globally available constants.
>> on preOpenStack
>> global g<app>Features
>> put "feature1,feature2,feature3" into g<app>Features
>> end preOpenStack
>> ...some other stack
>> global g<app>features
>> if "feature2" is among the items of g<app>features then
>> ...
>> on closeStackRequest
>> delete variable g<app>Features
>> end closestackRequest
>> great for A/B testing, rolling out new features without messing with existing code, being able to roll back unwanted or not-working features after beta testing... and would be so much cleaner if we didn't have to resort to global variables and remember to put a reference to them in each place they're referenced...
>> -- 
>> Mark Wieder
>> ahsoftware at
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> _______________________________________________
> 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