hwgui-developers — Discussing of HwGUI development

[Hwgui-developers] error on hwgui\samples\combobox\combobox.prg

[oleksa <m.o...@uk...>]

Run BoundDemo and click Combo1 button, get:

Error BASE/1099  Argument error: STR
Called from ->STR(0)
Called from combobox.prg->(b)BOUNDTEST(92)
Called from source\hdialog.prg->DLGCOMMAND(515)
Called from source\hdialog.prg->(b)(_INITSTATICS00003)(0)
Called from source\hdialog.prg->HDIALOG:ONEVENT(237)
Called from ->HWG_DLGBOXINDIRECT(0)
Called from source\hdialog.prg->HDIALOG:ACTIVATE(178)
Called from combobox.prg->BOUNDTEST(97)
Called from combobox.prg->(b)MAIN(23)
Called from source\hwindow.prg->ONCOMMAND(886)
Called from source\hwindow.prg->(b)HMAINWINDOW(253)
Called from source\hwindow.prg->HMAINWINDOW:ONEVENT(477)
Called from ->HWG_ACTIVATEMAINWINDOW(0)
Called from source\hwindow.prg->HMAINWINDOW:ACTIVATE(433)
Called from combobox.prg->MAIN(26)

HwGUI 2.17 Harbour 3.2.0dev (Rev. 18819)
Date:02/11/13
Time:16:54:50

nCombo change type from N to C.

Regards,
Alexey Myronenko

[Hwgui-developers] Error while scrolling in object inspector

[oleksa <m.o...@uk...>]

Hi!

Open example.xml form, in object inspector edit any value in combobox and then try to scroll by mouse, get the next error:

Error BASE/1004  Message not found: PBROWSE:NSCROLLBARS
Called from ->__ERRRT_SBASE(0)
Called from ../../../tobject.prg->PBROWSE:ERROR(0)
Called from ../../../tobject.prg->(b)HBOBJECT(0)
Called from ../../../tobject.prg->PBROWSE:MSGNOTFOUND(0)
Called from ../../../tobject.prg->PBROWSE:NSCROLLBARS(0)
Called from source\hcombo.prg->HCOMBOBOX:ONEVENT(331)
Called from ->HWG_ACTIVATEMAINWINDOW(0)
Called from source\hwindow.prg->HMAINWINDOW:ACTIVATE(433)
Called from designer.prg->_APPMAIN(349)

HwGUI 2.17 Harbour 3.2.0dev (Rev. 18819)
Date:02/11/13
Time:14:05:01

Regards,
Alexey Myronenko

Re: [Hwgui-developers] Error BASE/1004 Message not found: HFORMTMPL:TYPE

[oleksa <m.o...@uk...>]

Hi!

Is it enough to add the next lines (+) for correct work this func?

FUNCTION GetSkip( oParent, hCtrl, lClipper, nSkip )
   LOCAL i, nextHandle, oCtrl
   LOCAL oForm := iif( ( oForm := hwg_GetParentForm(oParent ) ) = Nil, oParent, oForm )
+  if oform:classname=="HFORMTMPL"
+     oForm := oForm:oDlg
+  endif
   DEFAULT nSkip := 1

Regards,
Alexey Myronenko


  --- Оригінальне повідомлення ---
 Від кого: "oleksa" <m.o...@uk...>
 Кому: hwg...@li...
 Дата: 7 лютого 2013, 13:12:00
 Тема: [Hwgui-developers] Error BASE/1004 Message not found: HFORMTMPL:TYPE
 
 


> Hi!
> 
> Try Test1 from hwgui\utils\designer\samples\example.prg and press the Tab key.
> 
> 
> Error BASE/1004  Message not found: HFORMTMPL:TYPE
> Called from ->__ERRRT_SBASE(0)
> Called from ../../../tobject.prg->HFORMTMPL:ERROR(0)
> Called from ../../../tobject.prg->(b)HBOBJECT(0)
> Called from ../../../tobject.prg->HFORMTMPL:MSGNOTFOUND(0)
> Called from ../../../tobject.prg->HFORMTMPL:TYPE(0)
> Called from source\hedit.prg->GETSKIP(1423)
> Called from source\hedit.prg->HEDIT:ONEVENT(358)
> Called from ->HWG_DLGBOXINDIRECT(0)
> Called from source\hdialog.prg->HDIALOG:ACTIVATE(178)
> Called from source\procmisc\hfrmtmpl.prg->HFORMTMPL:SHOW(428)
> Called from source\procmisc\hfrmtmpl.prg->(b)COMPILEMETHOD(539)
> Called from source\hownbtn.prg->HOWNBUTTON:MUP(470)
> Called from source\hownbtn.prg->HOWNBUTTON:ONEVENT(174)
> Called from ->HWG_ACTIVATEMAINWINDOW(0)
> Called from source\hwindow.prg->HMAINWINDOW:ACTIVATE(433)
> Called from source\procmisc\hfrmtmpl.prg->HFORMTMPL:SHOW(428)
> Called from source\procmisc\hfrmtmpl.prg->(b)HFORMTMPL(165)
> Called from source\procmisc\hfrmtmpl.prg->HFORMTMPL:SHOWMAIN(0)
> Called from example.prg->MAIN(21)
> 
> HwGUI 2.17 Harbour 3.2.0dev (Rev. 18819)
> Date:02/07/13
> Time:12:52:45
> 
> Regards,
> Alexey Myronenko
> 
> ------------------------------------------------------------------------------
> Free Next-Gen Firewall Hardware Offer
> Buy your Sophos next-gen firewall before the end March 2013 
> and get the hardware for free! Learn more.
> http://p.sf.net/sfu/sophos-d2d-feb
> _______________________________________________
> Hwgui-developers mailing list
> Hwg...@li...
> https://lists.sourceforge.net/lists/listinfo/hwgui-developers

[Hwgui-developers] Error BASE/1004 Message not found: HFORMTMPL:TYPE

[oleksa <m.o...@uk...>]

Hi!

Try Test1 from hwgui\utils\designer\samples\example.prg and press the Tab key.


Error BASE/1004  Message not found: HFORMTMPL:TYPE
Called from ->__ERRRT_SBASE(0)
Called from ../../../tobject.prg->HFORMTMPL:ERROR(0)
Called from ../../../tobject.prg->(b)HBOBJECT(0)
Called from ../../../tobject.prg->HFORMTMPL:MSGNOTFOUND(0)
Called from ../../../tobject.prg->HFORMTMPL:TYPE(0)
Called from source\hedit.prg->GETSKIP(1423)
Called from source\hedit.prg->HEDIT:ONEVENT(358)
Called from ->HWG_DLGBOXINDIRECT(0)
Called from source\hdialog.prg->HDIALOG:ACTIVATE(178)
Called from source\procmisc\hfrmtmpl.prg->HFORMTMPL:SHOW(428)
Called from source\procmisc\hfrmtmpl.prg->(b)COMPILEMETHOD(539)
Called from source\hownbtn.prg->HOWNBUTTON:MUP(470)
Called from source\hownbtn.prg->HOWNBUTTON:ONEVENT(174)
Called from ->HWG_ACTIVATEMAINWINDOW(0)
Called from source\hwindow.prg->HMAINWINDOW:ACTIVATE(433)
Called from source\procmisc\hfrmtmpl.prg->HFORMTMPL:SHOW(428)
Called from source\procmisc\hfrmtmpl.prg->(b)HFORMTMPL(165)
Called from source\procmisc\hfrmtmpl.prg->HFORMTMPL:SHOWMAIN(0)
Called from example.prg->MAIN(21)

HwGUI 2.17 Harbour 3.2.0dev (Rev. 18819)
Date:02/07/13
Time:12:52:45

Regards,
Alexey Myronenko

Re: [Hwgui-developers] To Maurizio (-3rd in hbp)

[oleksa <m.o...@uk...>]

What you mean when said about hbide (by Pritpal?) and hbide users? HbIde users monitoring hwgui project looking in hbp file? But Chanelog give more info.

Regards,
Alexey Myronenko

  --- Оригінальне повідомлення ---
 Від кого: "Maurizio la Cecilia" <m.l...@gm...>
 Кому: "oleksa" <m.o...@uk...>
 Дата: 4 лютого 2013, 17:29:56
 Тема: Re: [Hwgui-developers] To Maurizio (-3rd in hbp)
 
 


> Hi, 
> are just settings of hbide project  properties. 
> Free to delete them, but hbide users will see in svn the hbp file with changed state any time they will open the project. 
> BR 
> Maurizio 
> 
> Il giorno 04/feb/2013 14:49, "oleksa" <m.o...@uk...> ha scritto:
> >
> > Hi!
> >
> > Can you explain these lines in hwgui.hbp
> >
> > -3rd=hbide_version=1.0
> > -3rd=hbide_type=Lib
> > -3rd=hbide_title=hwgui
> > -3rd=hbide_output=hwgui
> >
> > Regards,
> > Alexey Myronenko
> >
> > ------------------------------------------------------------------------------
> > Everyone hates slow websites. So do we.
> > Make your web apps faster with AppDynamics
> > Download AppDynamics Lite for free today:
> > http://p.sf.net/sfu/appdyn_d2d_jan
> > _______________________________________________
> > Hwgui-developers mailing list
> > Hwg...@li...
> > https://lists.sourceforge.net/lists/listinfo/hwgui-developers

Re: [Hwgui-developers] To Maurizio (-3rd in hbp)

[Maurizio la C. <m.l...@gm...>]

Hi,
are just settings of hbide project  properties.
Free to delete them, but hbide users will see in svn the hbp file with
changed state any time they will open the project.
BR
Maurizio

Il giorno 04/feb/2013 14:49, "oleksa" <m.o...@uk...> ha scritto:
>
> Hi!
>
> Can you explain these lines in hwgui.hbp
>
> -3rd=hbide_version=1.0
> -3rd=hbide_type=Lib
> -3rd=hbide_title=hwgui
> -3rd=hbide_output=hwgui
>
> Regards,
> Alexey Myronenko
>
>
------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_jan
> _______________________________________________
> Hwgui-developers mailing list
> Hwg...@li...
> https://lists.sourceforge.net/lists/listinfo/hwgui-developers

[Hwgui-developers] To Maurizio (-3rd in hbp)

[oleksa <m.o...@uk...>]

Hi!

Can you explain these lines in hwgui.hbp

-3rd=hbide_version=1.0
-3rd=hbide_type=Lib
-3rd=hbide_title=hwgui
-3rd=hbide_output=hwgui

Regards,
Alexey Myronenko

Re: [Hwgui-developers] hcontrol():backstyle

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

Basso, Luis Fernando writes:
> Hi
> 
> BackStyle is an important property and is used in several classes. It is 
> independent of WS_EX_TRANSPARENT, which is used in labels and hyperlinks.
> Serves to define the style in shape and classas container, panel and group 
> and others.

  Yes, but we can set and use WS_EX_TRANSPARENT in all controls where it 
needed instead of using the :backstyle. We can replace checking of 
:backstyle by checking the WS_EX_TRANSPARENT flag in :extstyle and all 
will work as it works now, but without redundant :backstyle.

> I think the class HSTATIC PAINT method can not be removed from the codes 
> that enable transparency in objects.
> 
   For now, I've deleted the clause TRANSPARENT from the basic SAY 
command, it is in a SAY [EXTENDED | EXT], which preprocessed into 
HStaticEx, where Paint method exists.

Regards, Alexander.

Re: [Hwgui-developers] hcontrol():backstyle

[Basso, L. F. <lf...@vi...>]

Hi

BackStyle is an important property and is used in several classes. It is 
independent of WS_EX_TRANSPARENT, which is used in labels and hyperlinks.
Serves to define the style in shape and classas container, panel and group 
and others.
It was a way to standardize. It is used in conjunction with SetBkMode

I think the class HSTATIC PAINT method can not be removed from the codes 
that enable transparency in objects.

Regards, Basso

-----Mensagem Original----- 
From: Alexander S.Kresin
Sent: Wednesday, January 16, 2013 6:48 AM
To: hwg...@li...
Subject: [Hwgui-developers] hcontrol():backstyle

Hi,

  as I see, the hcontrol():backstyle variable may have only two values:
OPAQUE (default) and TRANSPARENT. But we already have the :extstyle
variable, which have the WS_EX_TRANSPARENT flag set if the control is
TRANSPARENT. So there is no any need in the hcontrol():backstyle, or I
miss something ?

Regards, Alexander.

------------------------------------------------------------------------------
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
and much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612
_______________________________________________
Hwgui-developers mailing list
Hwg...@li...
https://lists.sourceforge.net/lists/listinfo/hwgui-developers 

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

[Alex S. <ss...@mw...>]

On 2013/01/17 08:26 AM, Alexander S.Kresin wrote:
> Great! I never thought that this is possible. Could you provide 
> guilib.ch with appropriate changes ?
This idea is taken from Clip4Win written by John Skelton. He took some 
interest in Harbour in the early days, I really wish he had stuck 
around, it was an excellent library.

Yes, I'll do it.

-- 
Regards
Alex

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

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

Alex Strickland writes:
> 
> #xtranslate __IIF(.T., [<true>], [<false>]) => <true>
> #xtranslate __IIF(.F., [<true>], [<false>]) => <false>
> 
> #xcommand JOINSTR <a>, <b> [ <fcn: FCN> <fcnname> ] => ;
>          __IIF(<.fcn.>, <fcnname>, Join)(<a>, <b>)
> 
> 
> procedure main
> 
>      JOINSTR "a", "b"
> 
>      JOINSTR "a", "b" FCN MyJoin
> 
> return
> 
> procedure Join(a, b)
> 
> ? a + b
> 
> procedure MyJoin(a, b)
> 
> ? a + ", " + b
> 

  Great! I never thought that this is possible. Could you provide 
guilib.ch with appropriate changes ?

Regards, Alexander.

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

[Alex S. <ss...@mw...>]

On 2013/01/15 03:04 PM, Alexander S.Kresin wrote:
> It looks interesting for me. We could add this clause to all our 
> commands, but I can't make it to work - it gives errors while 
> compiling. And what is the __IIF ? 

Sorry, I did not give you the complete code, here is a minimal example 
with all that is required:

#xtranslate __IIF(.T., [<true>], [<false>]) => <true>
#xtranslate __IIF(.F., [<true>], [<false>]) => <false>

#xcommand JOINSTR <a>, <b> [ <fcn: FCN> <fcnname> ] => ;
         __IIF(<.fcn.>, <fcnname>, Join)(<a>, <b>)


procedure main

     JOINSTR "a", "b"

     JOINSTR "a", "b" FCN MyJoin

return

procedure Join(a, b)

? a + b

procedure MyJoin(a, b)

? a + ", " + b

-- 
Regards
Alex

[Hwgui-developers] hcontrol():backstyle

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

Hi,

  as I see, the hcontrol():backstyle variable may have only two values: 
OPAQUE (default) and TRANSPARENT. But we already have the :extstyle 
variable, which have the WS_EX_TRANSPARENT flag set if the control is 
TRANSPARENT. So there is no any need in the hcontrol():backstyle, or I 
miss something ?

Regards, Alexander.

Re: [Hwgui-developers] @ say TRANSPARENT not work

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

Itamar M. Lins Jr. Lins writes:
> Hi!
>  
> @ x,y say 'XXXXXXXXXX' size 100,20 Transparent
> Not work.
>  

  Fixed, see latest Changelog.
Now this command will be preprocessed to a call of HStaticEx and will 
work as expected.

Regards, Alexander.

[Hwgui-developers] @ say TRANSPARENT not work

[Itamar M. L. J. L. <ita...@gm...>]

Hi!

@ x,y say 'XXXXXXXXXX' size 100,20 Transparent
Not work.

Best regards,
Itamar M. Lins Jr.

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

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

Alex Strickland writes:

>> It doesn't really help in your situation now

  It is a key sentence :). It doesn't help in compatibility problem - 
people still need to change the syntax of appropriate commands.

>> but I always wished it 
>> was implemented for all relevant commands because then you are free to 
>> inherit from the HWGUI classes but you don't have to rewrite the 
>> command to use your new class. In this way the EX versions need not 
>> have created new commands unless they had new clauses. 

In our case all these EX versions have new clauses.

> No comments here ..., is it a bad idea?
> 

It looks interesting for me. We could add this clause to all our 
commands, but I can't make it to work - it gives errors while compiling. 
And what is the __IIF ?

Regards, Alexander.

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

[Alex S. <ss...@mw...>]

On 2013/01/10 04:47 PM, Alex Strickland wrote:
> It doesn't really help in your situation now but I always wished it 
> was implemented for all relevant commands because then you are free to 
> inherit from the HWGUI classes but you don't have to rewrite the 
> command to use your new class. In this way the EX versions need not 
> have created new commands unless they had new clauses. 
No comments here ..., is it a bad idea?

-- 
Regards
Alex

Re: [Hwgui-developers] Error while building hwgui (* $Id:Changelog1990)

[oleksa <m.o...@uk...>]

Yes, harbour is latest. Now build is ok. Thanks.

Regards,
Alexey Myronenko


  --- Оригінальне повідомлення ---
 Від кого: "Alexander S.Kresin" <al...@be...>
 Кому: hwg...@li...
 Дата: 14 січня 2013, 14:01:29
 Тема: Re: [Hwgui-developers] Error while building hwgui (* $Id:Changelog1990)
 
 


> oleksa ?????:
> > Hi!
> > 
> > source\hipedit.prg(46) Warning W0001  Ambiguous reference 'SUPER'
> > 
> > source\hipedit.prg(98) Warning W0001  Ambiguous reference 'SUPER'
> > 
> > source\hipedit.prg(124) Warning W0001  Ambiguous reference 'SUPER'
> > 
> 
> Do you use the latest Harbour from the SVN ? I suppose, that this 
> warnings are caused by the recent changes, made by Przemek - something 
> related to the 'super'. Try to replace it by '::super'.
> 
> Regards, Alexander.
> 
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
> _______________________________________________
> Hwgui-developers mailing list
> Hwg...@li...
> https://lists.sourceforge.net/lists/listinfo/hwgui-developers

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

[oleksa <m.o...@uk...>]

Ok, do it!

Regards,
Alexey Myronenko

  --- Оригінальне повідомлення ---
 Від кого: "Alexander S.Kresin" <al...@be...>
 Кому: hwg...@li...
 Дата: 15 січня 2013, 11:28:29
 Тема: Re: [Hwgui-developers] Some incompatibilities with previous versions
 
 


> 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.
> 
> ------------------------------------------------------------------------------
> Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
> and more. Get SQL Server skills now (including 2012) with LearnDevNow -
> 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only - learn more at:
> http://p.sf.net/sfu/learnmore_122512
> _______________________________________________
> Hwgui-developers mailing list
> Hwg...@li...
> https://lists.sourceforge.net/lists/listinfo/hwgui-developers

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

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

  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.

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

Re: [Hwgui-developers] Error while building hwgui (* $Id: Changelog 1990)

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

oleksa ?????:
> Hi!
> 
> source\hipedit.prg(46) Warning W0001  Ambiguous reference 'SUPER'
> 
> source\hipedit.prg(98) Warning W0001  Ambiguous reference 'SUPER'
> 
> source\hipedit.prg(124) Warning W0001  Ambiguous reference 'SUPER'
> 

   Do you use the latest Harbour from the SVN ? I suppose, that this 
warnings are caused by the recent changes, made by Przemek - something 
related to the 'super'. Try to replace it by '::super'.

Regards, Alexander.

[Hwgui-developers] Error while building hwgui (* $Id: Changelog 1990)

[oleksa <m.o...@uk...>]

Hi!

source\hipedit.prg(46) Warning W0001  Ambiguous reference 'SUPER'

source\hipedit.prg(98) Warning W0001  Ambiguous reference 'SUPER'

source\hipedit.prg(124) Warning W0001  Ambiguous reference 'SUPER'

No code generated.
hbmk2: Error: Running Harbour compiler (embedded). 1

Regards,
Alexey Myronenko

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

[oleksa <m.o...@uk...>]

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)> ]

because the minimum we need is

@ x,y say csay1 size 100,24

and in that case if the error is happened, the situation is not clear where, in hstatic or hstaticex.

And how it will look in the documentation:

... if you use the clause [ ON DBLCLICK <bDblClick> ] then works a hstaticex if no, then hstatic ...

again not clear for newbie.

In other case we will include the extended command even if we are not use them.

Regards,
Alexey Myronenko

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

[Alex S. <ss...@mw...>]

On 2013/01/10 02:37 PM, Alexander S.Kresin wrote:
> clauses are in these new commands. What is a most suitable way to
> provide compatibility is still an open question. For example, we can
> create a new .ch, where old SAY, BUTTON, GROUP commands will be related
> with new "ex" classes.

To allow using different classes with a command I did this (see CLASS 
clause):

#xcommand @ <x>,<y> GET [ <oEdit> VAR ] <vari>  ;
             [ OF <oWnd> ]              ;
             [ ID <nId> ]               ;
             [ SIZE <width>, <height> ] ;
             [ COLOR <color> ]          ;
             [ BACKCOLOR <bcolor> ]     ;
             [ PICTURE <cPicture> ]     ;
             [ WHEN  <bGfocus> ]        ;
             [ VALID <bLfocus> ]        ;
             [<lPassword: PASSWORD>]    ;
             [ MAXLENGTH <nMaxLength> ] ;
             [ STYLE <nStyle> ]         ;
             [<lnoborder: NOBORDER>]    ;
             [ FONT <oFont> ]           ;
             [ ON INIT <bInit> ]        ;
             [ TOOLTIP <ctoolt> ]       ;
             [ ON KEYDOWN <bKeyDown>   ];
             [ ON CHANGE <bChange> ]    ;
             [ ON CHANGE <bChange> ]    ;
             [ <class: CLASS> <classname> ] ;
           => ;
     [<oEdit> := ] __IIF(<.class.>, <classname>, HEdit)():New( 
<oWnd>,<nId>,<vari>,               ;
{|v|Iif(v==Nil,<vari>,<vari>:=v)},             ;
<nStyle>,<x>,<y>,<width>,<height>,<oFont>,<bInit>,,, ;
<bGfocus>,<bLfocus>,<ctoolt>,<color>,<bcolor>,<cPicture>,;
<.lnoborder.>,<nMaxLength>,<.lPassword.>,<bKeyDown>, <bChange>)

It doesn't really help in your situation now but I always wished it was 
implemented for all relevant commands because then you are free to 
inherit from the HWGUI classes but you don't have to rewrite the command 
to use your new class. In this way the EX versions need not have created 
new commands unless they had new clauses.

-- 
Regards
Alex