Bug Fix: The alphabetic ordering of ADD OBJECT's objects can cause that some objects be created in erroneous order, causing unexpected behavior (Jochen Kauz) [https://github.com/fdbozzo/foxbin2prg/issues/28]

NOTE: This Bug Fix implies that when tx2 files are regenerated, differences will occur almost certainly for the first time, so do not regenerate all tx2 files unnecesarily to keep differences at minimum.
This commit is contained in:
fdbozzo
2018-07-31 10:57:08 +02:00
parent a3533dac1e
commit bbaad331a5
27 changed files with 396 additions and 361 deletions

View File

@@ -34,14 +34,14 @@ DEFINE CLASS f_base1 AS f_base OF "lib_controles.vcx"
DoCreate = .T.
Name = "F_base1"
Command2.Name = "Command2"
Edit1.Name = "Edit1"
Edit1.Value = <fb2p_value>* En los OptionGroup subclasados, cuando el Option de la clase de base tiene Autosize=.T. y la instancia tiene Autosize=.F., ocurre esto:&#13; - Los option normales deben mantener su longitud y apariencia nuevos&#13; - Los option graficos deben mantener su longitud y apariencia, pero pierden en height (bug de VFP)&#13;* En los OptionGroup normales, no hay problemas y se deben mantener igual siempre&#13;&#13;* RECOMENDACI<43>N: No usar Autosize=.T. en una clase de base</fb2p_value>
Label3.Name = "Label3"
Command2.Name = "Command2"
Label1.Caption = "COMMANDGROUP NORMAL"
Label1.Name = "Label1"
Label2.Caption = "COMMANDGROUP SUBCLASADOS"
Label2.Name = "Label2"
Label3.Name = "Label3"
ADD OBJECT 'Cl_commandbutton1' AS cl_commandbutton WITH ;
Alignment = 2, ;