Fabio,

I have no problems that a strategy that make sense for visual objects will be used for non visual ones.
The bad part is that the whole stuff is not documented.

I agree that (for example) the idea to control the load order within a DE by ZORDER is very strange. And this is the only place where the order make any sense because the CA will be opend by load order and it is too bad to load the wrong CA first. And a newly added CA will always be on top of the ZORDER ::)

Anyway I do not use this (because in the moment I was starting using DE and CA I was not aware of this possibility and code around) nor do I use ZORDER except for some splitter-controls, and this is very restricted to ZORDER(0) and ZORDER(1). I have no need for tricky reordering (yet). If I have it would be very simple to implement a new property and some code. Please not that even programms that deal with grafics where the order is more important often use a simple forward backward strategy on that. For VFP the solution we have now is good enough.


Agnes
>
>Good Morning Fabio,
>
>yes I understand now that it will change the order events mentioned below. It seems quite logical that for example "REFRESH" will work in that order because it "paints" the one object over the next one. I would never trust any code in an event there that deal with sibblings. Such stuff (if realy needed) belongs to the parent container, or (for other reasons) to the form.
>
>Agnes
>
>
>Good Morning Agnes,
>
>I agree partially.
>
>- This is one rather rigid simplification:
>it can find sense for Refresh, but for Init and SetAll ?
>If you construct a not graphical container (a DE object) it is not much logic to control the index of Cursors and CursorAdapters with ZOrder.
>
>But the true issue is this:
>- Now, you and me know that
>when you change a object's ZOrder,
>you set it's index value to 1 or to ControlCount value,
>but who has written the documentation for ZOrder knew this?
>
>Two answers:
>Yes : then a Team's Member competence problem exists
>Not : then a Team competence problem problem exists
>
>Update:
>Now,
>if you want reorder the Zorder for multiple objects,
>you have to implement a "Top/Bottom Reverse global Order algorithm"
>( example 100 objects, put 51 before 50 ).
>If VFP it exposed the property object.ControlIndex in read/write mode
>you can do a multiple ZOrder with least operations.
>
>Fabio