The effect occured under Windows 8, not as a flash but as permanent color black on yellow.
Dieter
Search found 38 matches
- Thu Sep 19, 2013 4:15 am
- Forum: eXpress++ Support
- Topic: DATATOOLTIP {||lDataToolTips} TIPBLOCK {|i|aVBAusw[i,5]}
- Replies: 9
- Views: 12688
- Thu Sep 12, 2013 5:15 am
- Forum: eXpress++ Support
- Topic: DATATOOLTIP {||lDataToolTips} TIPBLOCK {|i|aVBAusw[i,5]}
- Replies: 9
- Views: 12688
Re: DATATOOLTIP {||lDataToolTips} TIPBLOCK {|i|aVBAusw[i,5]}
Hi Roger, I have looked into Xsample_152 of XSAMPLE5.PRG (dated 18.08.2008) and I'm confused. - by DCGETOPTIONS is defined TOOLTIPCOLOR with GRA_CLR_BLACK, GRA_CLR_CYAN, but the Tooltip is displayed as black on yellow! That is my problem. The display is in a very small FONT!(may be caused by the Sre...
- Tue Sep 10, 2013 7:06 am
- Forum: eXpress++ Support
- Topic: DATATOOLTIP {||lDataToolTips} TIPBLOCK {|i|aVBAusw[i,5]}
- Replies: 9
- Views: 12688
Re: DATATOOLTIP {||lDataToolTips} TIPBLOCK {|i|aVBAusw[i,5]}
Yes Tom that is the problem, it does not work in browse.
It is curious in version 1.8 it worked (for colors only).
Best regards
Dieter
It is curious in version 1.8 it worked (for colors only).
Best regards
Dieter
- Tue Sep 10, 2013 4:20 am
- Forum: eXpress++ Support
- Topic: DATATOOLTIP {||lDataToolTips} TIPBLOCK {|i|aVBAusw[i,5]}
- Replies: 9
- Views: 12688
DATATOOLTIP {||lDataToolTips} TIPBLOCK {|i|aVBAusw[i,5]}
Is it possible to change FONT and COLOR for the TIPBLOCK message?
TOOLTIPCOLOR and TOOLTIPFONT seem to have no influence.
Dieter
TOOLTIPCOLOR and TOOLTIPFONT seem to have no influence.
Dieter
- Tue Apr 30, 2013 9:31 am
- Forum: eXpress++ Support
- Topic: Sreen resolution
- Replies: 2
- Views: 6310
Re: Sreen resolution
Hello Roger,
many thanks for your hint. The definitions in the XPJ-file were
GUI=yes
LINK_FLAGS= /PM:PM
but that was not enough.
Following your hint I added at
COMPILE_FLAGS= ../dEXPRESS19 !
And that worked.
Thank You
Dieter
many thanks for your hint. The definitions in the XPJ-file were
GUI=yes
LINK_FLAGS= /PM:PM
but that was not enough.
Following your hint I added at
COMPILE_FLAGS= ../dEXPRESS19 !
And that worked.
Thank You
Dieter
- Tue Apr 30, 2013 7:06 am
- Forum: eXpress++ Support
- Topic: Sreen resolution
- Replies: 2
- Views: 6310
Sreen resolution
I have a problem to read the data of screen resolution. With the command nWidth := AppDeskTop():currentSize()[1] an error is displayed: oError:args : -> VALTYPE: U VALUE: NIL oError:canDefault : N oError:canRetry : N oError:canSubstitute: J oError:cargo : NIL oError:description : Parameter hat falsc...
- Wed Dec 05, 2012 9:27 am
- Forum: eXpress++ Support
- Topic: Screen resolution/ FONTs
- Replies: 1
- Views: 4434
Screen resolution/ FONTs
Up to now the windows in applications with a screen resolution of 1440x900 were perfect. Tests on a new notebook under Windows 8 with a screen resolution of 1900x1080 show the following effects: - all windows are much smaller - all FONTs are smaller - FRAMEsare too small - partwise the FONT settings...
- Thu Sep 16, 2010 6:15 am
- Forum: eXpress++ Support
- Topic: Problem with ENTER key
- Replies: 2
- Views: 6553
Problem with ENTER key
Hello, I have created a very complex window with a large number of SAY and GET fields, the GET fields with COMBO, LISTBOX, GOTFOCUS, LOSTFOCUS, HIDE etc, and DCREAD GUI. After some addtions now I have a very unfriendly effect. If at a GET field the ENTER key is pressed, most of the GET fields are bl...