|
From: Alexander S.K. <al...@be...> - 2013-01-15 09:28:25
|
So, if nobody objects, I'll change declarations of SAYEX, BUTTONX,
GROUPEX commands in guilib.ch in following way:
#xcommand @ <x>,<y> SAY [ <lExt: EXTENDED,EXT> ] [ <oSay> CAPTION ]
<caption> ;
[ OF <oWnd> ] ;
...
[ ON DBLCLICK <bDblClick> ];
...
=> ;
[<oSay> := ] HStaticEx():New(
...
After this change the following lines:
@ 20,10 SAY cText SIZE 260, 22
@ 20,10 SAY cText SIZE 260, 22 ON DBLCLICK {||MsgInfo("!")}
@ 20,10 SAY EXT cText SIZE 260, 22
will be preprocessed into:
HStatic():New(,,,20,10,260, 22,cText,,,,,,,,.F. );
HStaticEx():New(,,,20,10,260, 22,cText,,,,,,,,.F.,,{||MsgInfo("!")}, );
HStaticEx():New(,,,20,10,260, 22,cText,,,,,,,,.F.,,, );
Thus, if we use additional clauses, which demands functionality of "ex"
classes, the command will be preprocessed to a call of "ex" class (
HStaticEx, etc. ). If we don't use them, the command will be
preprocessed into a call of a base class ( HStatic, etc. ). I someone
want to use "ex" class independently of the comand clauses, he should
use "EXTENDED" or "EXT" word ( SAY EXT, etc. ).
Regards, Alexander.
|