Re: [Hwgui-developers] Some incompatibilities with previous versions

[Alexander S.K. <al...@be...>]

oleksa ?????:
> Hi!
> 
> If we decide to keep both in the same file, i suggest the next syntax
>  
> #xcommand @ <x>,<y> SAY EXTENDED [ <oSay> CAPTION ] <caption> ;
>               [ OF <oWnd> ]              ;
> ...
>            => ;
>            [<oSay> := ] HStaticEx():New( 
> <oWnd>,<nId>,<nStyle>,<x>,<y>,<width>, ;
>               <height>,<caption>,<oFont>,<bInit>,<bSize>,<bDraw>,<ctoolt>, ;
>               <color>,<bcolor>,<.lTransp.>,<bClick>,<bDblClick>,<bOther> );;
>            [ <oSay>:name := <(oSay)> ]
> 

   I like the 'SAY EXTENDED' as a replacement for 'SAYEX', but this 
doesn't solve the compatibility problem. For now people will get compile 
errors, if they use those additional clauses with SAY and they must 
change all such commands to SAYEx or SAY EXTENDED, or use other 
guilib.ch ( the same about GROUP, BUTTON, and, later, some others ). The 
solution, which I suggested, allows to get rid of errors and it is quite 
logical, I think: if someone use extra functionality, writing additional 
clauses in SAY command, "ex" class is called, if no - basic. IF a 
programmer want to use "ex" class in all cases, with any clauses, he 
should write SAY EXTENDED (or SAY EXT), we may provide this:

#xcommand @ <x>,<y> SAY [ <lExt: EXTENDED,EXT> ] [ <oSay> CAPTION ] 
<caption> ;
               [ OF <oWnd> ]              ;
  ...
               [ ON DBLCLICK <bDblClick> ];
  ...
            => ;
            [<oSay> := ] HStaticEx():New(
  ...

#xcommand @ <x>,<y> SAY [ <oSay> CAPTION ] <caption> ;
               [ OF <oWnd> ]              ;
  ...
            => ;
            [<oSay> := ] HStatic():New(
  ...


Regards, Alexander