Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
BUG a Top/Left/Height/Width get fire property_Assign
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Visual FoxPro Beta
Divers
Thread ID:
00911720
Message ID:
00913004
Vues:
21

But if you're trying to change the width beyond what anchoring does, why are you using the Anchor functionality at all?

Because :
- on VFP9, Anchor free me from the necessity to use a BINDEVENT() on Parent.Resize()
and this require code on Init, and .....
- on VFP9, for example, Anchor can set Top and Left good, but i want Overridde the Width ad Heigh only


Update: or more to the point, you claimed that it was destructive. Why? Your examples aren't demonstrating that: they're only demonstrating that the behavior exists.


This is not a behaviour, it is a bug.

Your demand is like saying:
the computation behaviour is : 1+1 return 33
Now, demonstrates to me where this calculation creates problems 
However, if just you do not see the problem,
this bug imposes that the operations made on XXXX_Assign
do not depend on the order and the number of calls,
practically the code does not have to be correlated between the several Assign
and the values assign to you must be invariant regarding the current values.

Example, this type of operations
Left_Assign(NewLeftvalue) -> set Left to NewLeftvalue + 1
Width_Assign() this read Left, and this read call Left_Assign(this.Left),
RESULT: Left is NewLeftvalue + 2 !
***
But another undoc behaviour exists:
when a AnchorRefresh is done, it call Move(....)
( then VFP9.Move() is a Method/Event like Refresh(), in fact i call this AnchorRefresh)
the sequence is
Control.Move(..new anchor values )
* i can stop it with NODEF
* if continue, Left_Assign,.... are called
* Parent.Resize() is called
From the first moment it is a good solution,
because it puts in the hands of the developer the AnchorRefresh event,
but, in practical, it complicates the use of _ the Assign.

Of course, I can find a solution, but this complicates the things enough.

Because the types of Anchor that can be defined are not very many,
the VFPT was little more flexible, could easy be added the 3/4 lacking types,
and the problem of the Anchor was closed.

Garrett, I do not have problems to find a solution
(obviously this demand time),
but to see that there is a simple solution
and to have to make thousand contortionism why it must
go around various problems are much stressful one.

Hi
Fabio
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform