Why does, as Paul suggests, changing the layer order in the Project Browser 
work, whereas changing the layer order explicitly does not? We know that layers 
cannot be assigned to a particular object class (like fields) but include all 
controls at once. Is it possible that the layer order of the fields only was 
not properly grokked?

Craig

> On Jul 28, 2023, at 10:19 AM, Mark Smith via use-livecode 
> <use-livecode@lists.runrev.com> wrote:
> 
> Thanks Paul. That is one of those super helpful tips that is hard to discover 
> on your own. 1 day we need an easily searchable wiki for all this acquired 
> wisdom (but for now I have tucked it away for future reference). Thanks for 
> replying.
> 
> Mark
> 
> 
>> On 28 Jul 2023, at 3:00 pm, Paul Dupuis via use-livecode 
>> <use-livecode@lists.runrev.com> wrote:
>> 
>> You can change the layer (order) in the Project Browser in the IDE by just 
>> dragging the objects up or down the list of objects on the card.
>> 
>> 
>> On 7/28/2023 6:19 AM, Mark Smith via use-livecode wrote:
>>> How do you reorder fields? I have a form (prebuilt) with 3 fields (a,b,c) 
>>> in positions 9, 15, 12 (as indicated by the Layer field in the Position 
>>> tab). Tabbing cause these fields to be visited in the order a, c, b whereas 
>>> I would prefer a, b, c. I have tried all manner of editing the Layer field 
>>> to make them be in that order with no success, I’ve variously tried new 
>>> orders: 9,10,11 or 14,15,16 or even 20,21,22 but nothing seems to affect 
>>> their order. It always returns to 9, 15, 12. Lock size and position is not 
>>> checked. I’ve even tried doing this with the Number field in the Advanced 
>>> tab, also without success. Ok, I did find a solution but while it was easy 
>>> for me, it might not be as easy on a more complicated form. I deleted all 3 
>>> fields. Recreated field A (which was given the starting position of 11) 
>>> then copy pasted two more times creating fields 12 and 13. So this 
>>> satisfies my reorder interest, but seems to me a rather cumbersome and 
>>> unnecessary procedure (if for no other reason than deleting fields also 
>>> deletes all of the “custom” settings on the fields which doubles or triples 
>>> the amount of effort involved). Maybe I am missing something more obvious?
>>> 
>>> Thanks
>>> 
>>> 
>>> _______________________________________________
>>> use-livecode mailing list
>>> use-livecode@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@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@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to