getting bogged down with the selectedObject

dsc at swcp.com dsc at swcp.com
Mon May 30 21:05:06 CEST 2016


Yikes.  That came out sounding rude.  Not my intent.  I'm just socially inept.  

And eventually you might want to handle the case of multiple selected objects.  

> On May 30, 2016, at 1:00 PM, Dar Scott <dsc at swcp.com> wrote:
> 
> Shouldn't the selected object list be empty in that case?  Can you check that?  
> 
> Or are you getting a crash in just doing this:
> 
> get the selectedObject
> 
> Dar
> darzLab
> 
> 
>> On May 30, 2016, at 12:43 PM, RM <richmondmathewson at gmail.com> wrote:
>> 
>> So; here I am mucking around with my alternative front-end and have a merry little button
>> with this script in it:
>> 
>> on mouseUp
>>  put fld "nname" into NN
>>  set the name of the selectedObject to NN
>> end mouseUp
>> 
>> which, unsurprisingly perhaps, changes the name of a selectedObject
>> in the topStack [which is what it is meant to do].
>> 
>> However, I cannot work out how to stop the button "throwing a bluey"
>> when nothing is selected.
>> 
>> Richmond.
>> 
>> _______________________________________________
>> 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




More information about the use-livecode mailing list