Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
More than one tab cycle
Message
De
05/08/2006 17:32:53
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
 
 
À
05/08/2006 14:46:26
Hans-Otto Lochmann
Dr. Lochmann Consulting Gmbh
Frankfurt, Allemagne
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
01142829
Message ID:
01143263
Vues:
9
>Hi Hilmar,
>
>>>
>>>In order to have Visible = .T. and in spite of that have the object to be "invisible" I just set Width and Height equal 0. It works!
>>
>>I would have considered putting it "off-limits", something like: TextBox.Left = 1000, but making it too small to see is also an interesting option.
>
>The idea is to have a "normally" placed and sized object in the design stage and to make it to disappear at runtime.

You can achieve this by setting this.left=-2*thisform.width in control's init. So it'll be there in design mode, and would hide far left before the form shows.

>So it was tempting to try to set Width and Height equal 0. I was really surprised, that is works. That means, that an object has an optical presentation, which is what you or the user sees, and a logical presention, which is what the runtime handles without taking note of the optical presentation.

Same goes with the far-out object - it can gain focus, its methods can run, it's as if it was completely live and kickin' (which it actually is). It's just out of sight.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform