Hello Roger,
thanks. That seems to work. Will this be part of the next build?
Search found 54 matches
- Fri Feb 26, 2010 1:35 am
- Forum: eXpress++ Support
- Topic: Question about automatic disabling childs
- Replies: 7
- Views: 15401
- Thu Feb 25, 2010 9:15 am
- Forum: eXpress++ Support
- Topic: Wrong display of DCRADIOBUTTON
- Replies: 2
- Views: 8436
Re: Wrong display of DCRADIOBUTTON
Hi Roger, it seems to depend of the xSize (Width)?!?! Please test with this code: #include "dcdialog.ch" PROCEDURE main LOCAL GetList := {}, cOption, oStatic, asize cOption := 'P' asize := { 150, 20} // asize := { , 20} // take this to see the problem @ 10, 10 DCSTATIC TYPE XBPSTATIC_TYPE_GROUPBOX S...
- Thu Feb 25, 2010 9:03 am
- Forum: eXpress++ Support
- Topic: Question about automatic disabling childs
- Replies: 7
- Views: 15401
Re: Question about automatic disabling childs
Hi,
not nice to hear. This would be very handy witj complex screens.
What do you think about the idea to look from the Child: If one of the parent is disabled, it should be diabled, too?
not nice to hear. This would be very handy witj complex screens.
What do you think about the idea to look from the Child: If one of the parent is disabled, it should be diabled, too?
- Thu Feb 25, 2010 8:15 am
- Forum: eXpress++ Support
- Topic: Question about automatic disabling childs
- Replies: 7
- Views: 15401
Re: Question about automatic disabling childs
Hi Roger, please test the following: #include "dcdialog.ch" function Appsys() return NIL procedure main() local getlist := {}, getoptions := {}, lRet, oStatic, cVar1 := space(10), cVar2 := (10), cVar3 := (10), lAktiv := .t. @ 3,3 DCSTATIC TYPE XBPSTATIC_TYPE_GROUPBOX SIZE 20, 4 OBJECT oStatic WHEN {...
- Thu Feb 25, 2010 6:21 am
- Forum: eXpress++ Support
- Topic: Wrong display of DCRADIOBUTTON
- Replies: 2
- Views: 8436
Wrong display of DCRADIOBUTTON
Hello Roger, i have still a problem with displaying DCRADIOBUTTONs (there was a thread several month ago in webboard). 1. It seems that vertical alignment is *very* Bottom, so some characters are cut ("g" for example) 2. Using "OPTIONS BS_VCENTER" leads to a Pushbutton-Style (without using BS_PUSHBU...
- Thu Feb 25, 2010 1:26 am
- Forum: eXpress++ Support
- Topic: Question about automatic disabling childs
- Replies: 7
- Views: 15401
Question about automatic disabling childs
Hello Roger, is it possible to have automatic disabled childs, if the parent is disabled about his WHEN-Block? Sample: I have a DCSTATIC Groupbox with 20 DCGETS on it. Now i would expect, that they are disabled, if the whenblock of the DCSTATIC is .f. This would help much in complex dialogs. Is this...
- Thu Feb 25, 2010 1:06 am
- Forum: eXpress++ Support
- Topic: Focus-Autorestore
- Replies: 2
- Views: 8483
Re: Focus-Autorestore
rdonnay wrote:I spent some time on this today and don't think I will be successful.
We hear this often at our support, when users switch to another window to copy data (exp. Phonenumber, partnumber) to my DCGETs...
- Tue Feb 23, 2010 1:11 am
- Forum: eXpress++ Support
- Topic: DCGET focus on mouseclick
- Replies: 4
- Views: 12489
Re: DCGET focus on mouseclick
Thanks. What about click in alpha-gets? See my both scenarios in first posting, please. Are both okay with 253?Tom wrote:Hi, Markus.
No eaten buffer with build 253.
A click into numeric gets works as expected.
- Mon Feb 22, 2010 9:38 am
- Forum: eXpress++ Support
- Topic: DCGET focus on mouseclick
- Replies: 4
- Views: 12489
Re: DCGET focus on mouseclick
Hi Roger,
therefore i made the suggestion for the "Changes"-Thread.
@Tom:
Did you use 253? Is the behaviour like expected?
Perhaps you can test the "Cutting with ContextMenu 'eats buffer"-problem, too Thanks.
therefore i made the suggestion for the "Changes"-Thread.
@Tom:
Did you use 253? Is the behaviour like expected?
Perhaps you can test the "Cutting with ContextMenu 'eats buffer"-problem, too Thanks.
- Mon Feb 22, 2010 7:27 am
- Forum: eXpress++ Support
- Topic: DCGET focus on mouseclick
- Replies: 4
- Views: 12489
DCGET focus on mouseclick
Hello Roger, at 5/4/2009 Tom Liehr starts this Thread in old webboard. It is about how the cursor should be positioned after clicking in a dcget. Did you found time to look into this? I think you could/should make two improvements: 1. Clicking in "space" after real characters should bring the cursor...