Hi, Nolberto. You don't have a problem with the size settings, but there is a lost workarea reference (alias) inside the to-be-resized-dialog. Refreshing the dialog (after resize) rereads the values of the dialog elements. And at least one of those points to a workarea which is not available anymore...
Hi, Jack. An empty static of the type XBPSTATIC_TYPE_TEXT - or just simply "DCSAY", which is almost the same - is a good invisible parent for lots of situations. If you have a combo box and don't want your (automatically sized, using DCREAD ... FIT) dialog to show an empty area below the combo, just...
CueBanner only works if the fields/vars are really empty. This will show a cuebanner: cMyVar1 := "" cMyVar2 := "" @ 1,1 DCSAY 'Test:' GET cMyVar1 GETSIZE 30 GETEVAL {|o|o:CueBanner := 'Enter Text'} @ 2,1 DCSAY 'Test:' GET cMyVar2 GETSIZE 30 GETEVAL {|o|o:CueBanner := 'Enter Text'} DCREAD GUI ADDBUTT...
what's the problem with public variables? Advantages: 1. PUBLICs are visible everywhere, even in different threads. 2. PUBLICs can be initialized in a function, they get visible "above". 3. PUBLICs can be stored to/restored from a XPF-file (as PRIVATEs). 4. PUBLICs can be changed everywhere, change...
Move all accesses/assignments to the var(s) to a get/set-function which sets the value or returns it. Place your debug code there (use DC_CallStack). Do you work with XPF-files and "RESTORE FROM" / "SAVE TO"? Maybe you restore the value there.
Hi, Fred. The errors you get may have something to do with the fact that the tooltip system runs in a different thread. You don't have access to your workareas there! It's quite hard to display tool tips depending on data in a workarea. Your gets need to set values in get/set-functions or even publi...