Search found 1174 matches
- Wed May 11, 2011 7:18 am
- Forum: eXpress++ Support
- Topic: Lock errro
- Replies: 5
- Views: 10190
Re: Lock errro
Hi, Fred. This condition is never true: DO WHILE .NOT. ( XLOCK := RLOCK() ) xLock := RLock() means xLock becomes RLock(). This happens anyway, even if RLock returns false. This should be correct: DO WHILE .NOT. ( XLOCK = RLOCK() ) Your app worked so far by mistake: This (a failing lock) simply never...
- Thu May 05, 2011 4:09 pm
- Forum: eXpress++ Support
- Topic: Resizing - show windows overlapping, side by side and others
- Replies: 0
- Views: 4746
Resizing - show windows overlapping, side by side and others
Since Windows XP, a user is able to right-click on the task bar and select "show windows overlapping/side by side ...". If the layout of an app is based on a more ... conservative approach, this will cause (especially with a MDI-app which generates windows for each instance/document/module) a very u...
- Thu Apr 14, 2011 10:38 am
- Forum: eXpress++ Support
- Topic: PRINT TO MULTIPLE PRINTERS SIMULTANEOUSLY
- Replies: 4
- Views: 9422
Re: PRINT TO MULTIPLE PRINTERS SIMULTANEOUSLY
Code: Select all
DCPRINT ON ... NAME <cMyPrinterName>
... print
DCPRINT OFF- Thu Apr 07, 2011 2:19 am
- Forum: eXpress++ Support
- Topic: Error WINDOWHEIG WindowWidth DCGETOPTIONS 880 710 NOMAXBUTTO
- Replies: 19
- Views: 25969
Re: Error WINDOWHEIG WindowWidth DCGETOPTIONS 880 710 NOMAXBUTTO
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...
- Thu Apr 07, 2011 2:12 am
- Forum: eXpress++ Support
- Topic: Static with no border
- Replies: 3
- Views: 7852
Re: Static with no border
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...
- Wed Apr 06, 2011 9:03 am
- Forum: eXpress++ Support
- Topic: cueBanner / showBalloon
- Replies: 12
- Views: 18963
Re: cueBanner / showBalloon
Yeah.When you refer to your sample, I assume you mean this?
- Wed Apr 06, 2011 8:58 am
- Forum: eXpress++ Support
- Topic: cueBanner / showBalloon
- Replies: 12
- Views: 18963
Re: cueBanner / showBalloon
This is from your code. Win XP (other sample was on 7), visual styles enabled, theme enabled. Second get has focus:
- Wed Apr 06, 2011 8:46 am
- Forum: eXpress++ Support
- Topic: cueBanner / showBalloon
- Replies: 12
- Views: 18963
Re: cueBanner / showBalloon
This is from my sample code (1st get has focus, so no banner is shown):
- Wed Apr 06, 2011 8:13 am
- Forum: eXpress++ Support
- Topic: cueBanner / showBalloon
- Replies: 12
- Views: 18963
Re: cueBanner / showBalloon
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...
- Mon Apr 04, 2011 1:25 pm
- Forum: Xbase++ Support
- Topic: debug issue
- Replies: 15
- Views: 25403
Re: debug issue
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...