Stack name conflicts resolved?

Ben Rubinstein benr_mc at cogapp.com
Mon Nov 7 13:17:01 CET 2016


On 06/11/2016 20:50, Monte Goulding wrote:
>
>> On 7 Nov. 2016, at 3:57 am, Mark Wieder <ahsoftware at sonic.net> wrote:
>>
>> Now rename the second stack to "Untitled 1"
>>
>> The property inspector allows this, but now gets very confused.
>
> Ah… well that’s probably a bug. If the IDE can’t handle multiple stacks with the same name it should not allow this. Even if the IDE were refactored to only refer to stacks by long ID it would still get confused by multiple stacks with the same name that are unsaved. I think the solution is a more robust object handle we can use in scripts it would help I think. Ideally we can get a handle to an object and pass it around and it won’t matter how much we change the ID or name of the object the handle will still be valid. If we had that then we could get lists of stack handles and not get confused if there are multiple with the same name.
>

My proposal in 2004 http://quality.livecode.com/show_bug.cgi?id=1061#c8 was 
for the IDE to create not a UUID but a unique-in-this-session "stackID" (since 
'id' of a stack is actually used for 'next ID'). There would thus be a way to 
refer to stacks within the IDE completely uniquely.

Modifying all code in the IDE that referenced stacks would doubtless be quite 
a large task; but once there is a way to reference stacks that is completely 
unique, then fixing particular identified issues caused by stacks with the 
same name would become simpler. Currently if I understand it correctly there 
are issues which seem just too hard to fix: so instead 
http://quality.livecode.com/show_bug.cgi?id=143 - the most egregious of these 
issues - was 'fixed' by adding the check that Richard's trying to remove.

Ben



More information about the use-livecode mailing list