You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
(64) |
Apr
(70) |
May
(54) |
Jun
(57) |
Jul
(34) |
Aug
(19) |
Sep
(28) |
Oct
(48) |
Nov
(42) |
Dec
(43) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(50) |
Feb
(19) |
Mar
(10) |
Apr
(5) |
May
(1) |
Jun
(14) |
Jul
(23) |
Aug
(6) |
Sep
(118) |
Oct
(110) |
Nov
(36) |
Dec
(6) |
| 2006 |
Jan
(19) |
Feb
(7) |
Mar
(4) |
Apr
(32) |
May
(6) |
Jun
(14) |
Jul
(42) |
Aug
(38) |
Sep
(88) |
Oct
(21) |
Nov
(40) |
Dec
(37) |
| 2007 |
Jan
(31) |
Feb
(20) |
Mar
(26) |
Apr
(38) |
May
(4) |
Jun
(3) |
Jul
(3) |
Aug
(8) |
Sep
(2) |
Oct
(3) |
Nov
(25) |
Dec
(9) |
| 2008 |
Jan
(7) |
Feb
(10) |
Mar
(16) |
Apr
(10) |
May
(25) |
Jun
(16) |
Jul
(27) |
Aug
(8) |
Sep
(20) |
Oct
(54) |
Nov
(11) |
Dec
(14) |
| 2009 |
Jan
(28) |
Feb
(22) |
Mar
(13) |
Apr
(70) |
May
(25) |
Jun
(23) |
Jul
(12) |
Aug
(18) |
Sep
(7) |
Oct
(4) |
Nov
(8) |
Dec
(36) |
| 2010 |
Jan
(58) |
Feb
(66) |
Mar
(3) |
Apr
(16) |
May
(9) |
Jun
(10) |
Jul
(6) |
Aug
(8) |
Sep
(17) |
Oct
(15) |
Nov
(12) |
Dec
(27) |
| 2011 |
Jan
(3) |
Feb
(17) |
Mar
(5) |
Apr
(12) |
May
(1) |
Jun
|
Jul
(1) |
Aug
(5) |
Sep
(56) |
Oct
(24) |
Nov
(8) |
Dec
(32) |
| 2012 |
Jan
(20) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(9) |
Jul
(29) |
Aug
(3) |
Sep
(17) |
Oct
(60) |
Nov
(17) |
Dec
(52) |
| 2013 |
Jan
(22) |
Feb
(35) |
Mar
(31) |
Apr
(5) |
May
(16) |
Jun
(108) |
Jul
(57) |
Aug
(2) |
Sep
(11) |
Oct
|
Nov
(3) |
Dec
(13) |
| 2014 |
Jan
(39) |
Feb
(15) |
Mar
|
Apr
(31) |
May
|
Jun
(9) |
Jul
(16) |
Aug
(1) |
Sep
(8) |
Oct
(51) |
Nov
(5) |
Dec
(119) |
| 2015 |
Jan
(78) |
Feb
(47) |
Mar
(25) |
Apr
(32) |
May
(34) |
Jun
(42) |
Jul
(62) |
Aug
(10) |
Sep
(11) |
Oct
(5) |
Nov
(13) |
Dec
(24) |
| 2016 |
Jan
(12) |
Feb
(1) |
Mar
(2) |
Apr
|
May
(1) |
Jun
(12) |
Jul
(5) |
Aug
(32) |
Sep
(36) |
Oct
(34) |
Nov
(3) |
Dec
(1) |
| 2017 |
Jan
(2) |
Feb
(3) |
Mar
(2) |
Apr
|
May
(3) |
Jun
(5) |
Jul
(6) |
Aug
(5) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2018 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(26) |
Sep
(24) |
Oct
(2) |
Nov
(6) |
Dec
(26) |
| 2019 |
Jan
(10) |
Feb
(5) |
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
(3) |
Aug
|
Sep
(2) |
Oct
(1) |
Nov
(1) |
Dec
(2) |
| 2020 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(4) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
|
From: Alexander S.K. <al...@be...> - 2013-07-03 06:01:04
|
>> Do you see any drawbacks in moving __DBGPROCESSRUN() to >> different file and removing dbgentry.c from HWGUI? >> > > No drawbacks at all. I get more satisfaction, when I remove some code, > staying with the same functionality, than when I add some :). > That function, __DBGPROCESSRUN(), was introduced, because > hb_processOpen() doesn't worked under Linux in the same way as under > Windows. I was tired to fight with it and wrote this one. > There is one problem, which I remembered now, the reason, why I included the dbgentry.c in HwGUI. In Harbour this file is a part of hbdebug.lib, so I need to link the hbdebug and there may be conflicts with some functions from debugger.prg, especially __dbgEntry(). What to do with this ? Regards, Alexander. |
|
From: Alexander S.K. <al...@be...> - 2013-07-03 05:46:59
|
Itamar M. Lins Jr. Lins writes: > I am frustrated with this new hwgui 2.18 > It was not the correct way to upgrade the version was dropped 2.17 and > is now being added through feedback by users, this strategy was very bad > for users, we are reporting all errors that had been fixed in version 2.17 > What errors does you mean ? All, what you reported, wasn't errors, these was some features, added in 2.17 and absent in 2.18. > I still can not use version 2.18 because it is totally incompatible with > 2.17 Why don't you send here full list of 2.17 features, which you use and which absent in 2.18 ? I'm sure that it isn't too long, and we may decide what to do with it. > > was better to correct the deficiencies of the 2.17 version with flag > "DHWG_USE_POINTER_ITEM" Just one question: who is the volunteer to correct this in 2.17 ? Not me. I've told here already, that I can't spend my time, digging in the complicated, labyrinthine and messy 2.17 code. Unfortunately, the HWG_USE_POINTER_ITEM mode isn't the only problem of 2.17. There are many bugs, but the quality of the code makes it difficult to fight with them. I told all this many times already ... So, for me that was the only way. I know, that such changes are very annoying for users. I'm a user of some other software products, too, and I know very well, what it is. That's why I try to solve the incompatibilities, which you and other people send me, but, of course, I don't reproduce those, which I consider wrong. Regards, Alexander. |
|
From: Alexander S.K. <al...@be...> - 2013-07-03 05:19:35
|
Przemyslaw Czerpak writes: > > After above reformatting it's possible to easy compare dbgentry.c from > HWGUI and Harbour. As I can see there is only one difference. In HWGUI > dbgentry.c contains new function __DBGPROCESSRUN() > If it's possible then I'd like to ask you move this function to different > file and remove redundant code. In longer terms it will create problems > and additional jobs for HWGUI and Harbour developers to keep synced the > same code, i.e. I'd like to commit some modifications to Harbour > repository to fix few potential problems when module names are not > correctly recognized so breakpoints do not work as expected. > > Do you see any drawbacks in moving __DBGPROCESSRUN() to > different file and removing dbgentry.c from HWGUI? > No drawbacks at all. I get more satisfaction, when I remove some code, staying with the same functionality, than when I add some :). That function, __DBGPROCESSRUN(), was introduced, because hb_processOpen() doesn't worked under Linux in the same way as under Windows. I was tired to fight with it and wrote this one. Regards, Alexander. |
|
From: Itamar M. L. J. L. <ita...@gm...> - 2013-07-02 23:29:59
|
>As i see, you didn't read all the latest post carefully, because yo>u think so, that people who discussing this question, make a wrong >choice. If you have app in production, you doesn't must update ever>y time hwgui and your app now, while you see any changes in repo. I> suggest you reread all the post (i think) from december 2012, and >decide for youself what is better, but every post from us about err>or, warning and etc in current version is a help for Alexander, mak>e hwgui better. Hi! Yes I am reading the emails, only the strategy adopted, I believe that was not the best, all modifications, additions, corrections to release 2.17 yes, were dismissed are not at version 2.18 now being added. I do not know how many developers were using release 2.17. It seems that none of you were using version 2.17 Best regards, Itamar M. Lins Jr. |
|
From: Przemyslaw C. <dr...@po...> - 2013-07-02 20:02:10
|
On Tue, 02 Jul 2013, Przemyslaw Czerpak wrote: > 2013-07-02 21:49 UTC+0200 Przemyslaw Czerpak (druzus/at/priv.onet.pl) > * hwgui/source/common/debug/dbgentry.c > * reformatted keeping the same rules as used to format dbgentry.c in > Harbour GIT repository. Hi Alexander, After above reformatting it's possible to easy compare dbgentry.c from HWGUI and Harbour. As I can see there is only one difference. In HWGUI dbgentry.c contains new function __DBGPROCESSRUN() If it's possible then I'd like to ask you move this function to different file and remove redundant code. In longer terms it will create problems and additional jobs for HWGUI and Harbour developers to keep synced the same code, i.e. I'd like to commit some modifications to Harbour repository to fix few potential problems when module names are not correctly recognized so breakpoints do not work as expected. Do you see any drawbacks in moving __DBGPROCESSRUN() to different file and removing dbgentry.c from HWGUI? best regards Przemek |
|
From: Przemyslaw C. <dr...@po...> - 2013-07-02 19:49:39
|
2013-07-02 21:49 UTC+0200 Przemyslaw Czerpak (druzus/at/priv.onet.pl)
* hwgui/source/common/debug/dbgentry.c
* reformatted keeping the same rules as used to format dbgentry.c in
Harbour GIT repository.
best regards
Przemek
|
|
From: oleksa <m.o...@uk...> - 2013-07-02 19:38:15
|
Hi! As i see, you didn't read all the latest post carefully, because you think so, that people who discussing this question, make a wrong choice. If you have app in production, you doesn't must update every time hwgui and your app now, while you see any changes in repo. I suggest you reread all the post (i think) from december 2012, and decide for youself what is better, but every post from us about error, warning and etc in current version is a help for Alexander, make hwgui better. Regards, Alexey Myronenko --- Оригінальне повідомлення --- Від кого: "Itamar M. Lins Jr. Lins" <ita...@gm...> Дата: 2 липня 2013, 21:42:49 > I am frustrated with this new hwgui 2.18 > It was not the correct way to upgrade the version was dropped 2.17 and is now being added through feedback by users, this strategy was very bad for users, we are reporting all errors that had been fixed in version 2.17 > > > > > > I still can not use version 2.18 because it is totally incompatible with 2.17 > > > > was better to correct the deficiencies of the 2.17 version with flag "DHWG_USE_POINTER_ITEM" and create a version 2.17a and then from 2:18 to release > > > > Best regards, > Itamar M. Lins Jr. > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > > _______________________________________________ > Hwgui-developers mailing list > Hwg...@li... > https://lists.sourceforge.net/lists/listinfo/hwgui-developers |
|
From: Itamar M. L. J. L. <ita...@gm...> - 2013-07-02 18:42:44
|
I am frustrated with this new hwgui 2.18 It was not the correct way to upgrade the version was dropped 2.17 and is now being added through feedback by users, this strategy was very bad for users, we are reporting all errors that had been fixed in version 2.17 I still can not use version 2.18 because it is totally incompatible with 2.17 was better to correct the deficiencies of the 2.17 version with flag "DHWG_USE_POINTER_ITEM" and create a version 2.17a and then from 2:18 to release Best regards, Itamar M. Lins Jr. |
|
From: Itamar M. L. J. L. <ita...@gm...> - 2013-07-01 13:13:16
|
@ 10,10 get oEdit var cEdit SIZE 50,50 ON KEYDOWN {|k,o|
ProcessaTecla(k,o)}
Syntax error "syntax error at '@'"
Best regards
Itamar M. Lins Jr.
|
|
From: Itamar M. L. J. L. <ita...@gm...> - 2013-07-01 13:00:10
|
@ 005,210 get CheckBox oTransp Var cTransp Caption "Transparent" Transparent Size 140,20 Syntax error "syntax error at '@'" Best regards, Itamar M. Lins Jr. |
|
From: Alexander S.K. <al...@be...> - 2013-07-01 12:03:55
|
Hello,
New utility, HwGUI tutorial has been added as hwgui/utils/tutorial.
Two bat files, for bcc55 and mingw are included. They create two exe's
- hwgrun.exe and the tutorial - tutor.exe.
It is interactive - because you can not only read the code and
comments, but execute it. Moreover, you can edit the code and then
execute it immedeately to see the results of your changes.
The tutorial is very simple to navigate, it has minimum of tools.
Just click on a tree node to see appropriate content is a text editor.
If this is a code fragment, double clicking on this tree node or
clicking on a button, which is in a right top corner of a window above
the editor will execute this code.
There is a configuration file, tutor.xml, which, possible, you
will need to tune.
It contains a tag with a path to HwGUI directory:
<hwgui_dir path="..\.." />
This path is needed for internal compiler to find the HwGUI
include/ directory with header file hwgui.ch, if the path is wrong, you
will get a message "compile error", when you will try to execute a code.
By default it is set to "..\.." due to the default location of this
program ( hwgui\utils\tutorial ). If you for some reason decide to
change this location, you will need to change this path.
Yet another tag, which you, probably, may want to change is:
<tutorial file="tutor_eng.xml" />
This is a name of a file with tutorial content. The default file
above "tutor_eng.xml" is an English language version. If there is some
other with a language of your choice, edit that tag.
There is some content already, we need to add new code and comments
to make it really full.
For Harbour there is no need to have even the harbour.exe to compile
and execute code, becouse Harbour have internal compiler library. As
far, as I know, xHarbour hasn't, so I've added some code specially for
xHarbour to compile code fragments with harbour.exe, to force it to work
you need to set the <harbour_bin> tag in tutor.xml.
Regards, Alexander.
|
|
From: Alexander S.K. <al...@be...> - 2013-07-01 07:29:08
|
Itamar M. Lins Jr. Lins ?????:
> Syntax error "syntax error at 'DIALOG'"
>
> Please add.
> From: Guilib.ch 2.17
>
> #xcommand ACTIVATE DIALOG <oDlg> ;
> [ <lNoModal: NOMODAL> ] ;
> [ SHOW <nShow>] ;
> [ ON ACTIVATE <bInit> ] ;
> => ;
> <oDlg>:Activate(<.lNoModal.>, <bInit>, <nShow> )
>
Maybe, it's better to do this command similar to ACTIVATE WINDOW:
#xcommand ACTIVATE DIALOG <oDlg> ;
[<lMaximized: MAXIMIZED>] ;
[<lMinimized: MINIMIZED>] ;
[<lCenter: CENTER>] ;
[ ON ACTIVATE <bInit> ] ;
I find it illogical, that these two command have so different sytax.
What are you think ?
Regards, Alexander.
|
|
From: Alexander S.K. <al...@be...> - 2013-07-01 07:24:47
|
Itamar M. Lins Jr. Lins ?????:
> @ 10,10 Browse oBrw DataBase of oDlg Size 400,200 ;
> WHEN {||fWhen(oBrw)}
>
> Error E0030 Syntax error "syntax error at '{'"
>
In 2.17 WHEN clause is simply an other name for ON GETFOCUS, and I
think that in this case it is a bad name, because BROWSE isn't a GET
object ( we use WHEN and WHILE for GET objects, aren't we ? ). The same
about VALID, which is used there as a synonym for ON LOSTFOCUS.
So, I recommend you to change WHEN to ON GETFOCUS, this will work in
both 2.17 and 2.18.
Regards, ALexander.
|
|
From: Itamar M. L. J. L. <ita...@gm...> - 2013-06-28 19:52:52
|
@ 10,10 Browse oBrw DataBase of oDlg Size 400,200 ;
WHEN {||fWhen(oBrw)}
Error E0030 Syntax error "syntax error at '{'"
Best regards,
Itamar M. Lins Jr.
|
|
From: Itamar M. L. J. L. <ita...@gm...> - 2013-06-28 19:47:17
|
Syntax error "syntax error at 'DIALOG'"
Please add.
From: Guilib.ch 2.17
#xcommand ACTIVATE DIALOG <oDlg> ;
[ <lNoModal: NOMODAL> ] ;
[ SHOW <nShow>] ;
[ ON ACTIVATE <bInit> ] ;
=> ;
<oDlg>:Activate(<.lNoModal.>, <bInit>, <nShow> )
Best regards,
Itamar M. Lins Jr.
|
|
From: Maurizio la C. <m.l...@gm...> - 2013-06-28 10:29:18
|
Il 28/06/2013 12:14, Alexander S.Kresin ha scritto: > Maurizio la Cecilia writes: > >> Hi Alex, >> please test the sample below. > Yes, I.see. This is a pointers issue, too. If recompile both hwgui and > hwg_extctrl without HWG_USE_POINTER_ITEM, the icon is drawn. > In 2.17 with HWG_USE_POINTER_ITEM it isn't drawn, as here. > Something wrong in theme.c Sure. > >> Note that also the tooltip doesn't display. > Displays already, after the recent fix. You're right. I just updated and rebuilt: the tooltip appears correctly. Thanks a lot. > > Regards, Alexander. BR Maurizio > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Hwgui-developers mailing list > Hwg...@li... > https://lists.sourceforge.net/lists/listinfo/hwgui-developers > > |
|
From: Alexander S.K. <al...@be...> - 2013-06-28 10:15:41
|
Maurizio la Cecilia writes:
> Hi Alex,
> please test the sample below.
Yes, I.see. This is a pointers issue, too. If recompile both hwgui and
hwg_extctrl without HWG_USE_POINTER_ITEM, the icon is drawn.
In 2.17 with HWG_USE_POINTER_ITEM it isn't drawn, as here.
Something wrong in theme.c
> Note that also the tooltip doesn't display.
Displays already, after the recent fix.
Regards, Alexander.
|
|
From: Maurizio la C. <m.l...@gm...> - 2013-06-28 09:10:56
|
Hi Alex,
please test the sample below.
Note that also the tooltip doesn't display.
#include "hwgui.ch"
#include "hwg_extctrl.ch"
local oDlg
INIT DIALOG oDlg TITLE "No icon neither tooltip on ButtonEx" ;
AT 190,10 SIZE 360,240
@ 20,190 BUTTONEX "Ok" SIZE 130, 32;
ICON HIcon():AddFile( "ok.ico" ):handle ;
ON CLICK {|| oDlg:Close()} ;
TOOLTIP "This button should contain an icon" ;
TRANSPARENT
oDlg:Activate()
TIA
Maurizio
2013/6/28 Alexander S.Kresin <al...@be...>
> Maurizio la Cecilia ?????:
> > Please, note that the buttonex control no more displays the icon.
> > BR
> > Maurizio
> >
> >
> Could you provide a short sample ? I still haven't any code, which
> demonstrates buttonex features.
>
> Regards, Alexander.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Hwgui-developers mailing list
> Hwg...@li...
> https://lists.sourceforge.net/lists/listinfo/hwgui-developers
>
|
|
From: Alexander S.K. <al...@be...> - 2013-06-28 07:36:56
|
Maurizio la Cecilia ?????: > Please, note that the buttonex control no more displays the icon. > BR > Maurizio > > Could you provide a short sample ? I still haven't any code, which demonstrates buttonex features. Regards, Alexander. |
|
From: Maurizio la C. <m.l...@gm...> - 2013-06-28 07:06:13
|
Please, note that the buttonex control no more displays the icon. BR Maurizio |
|
From: Itamar M. L. J. L. <ita...@gm...> - 2013-06-27 13:17:21
|
INIT WINDOW oFormMain MAIN AT 0,0 SIZE 100,100 ;
On Init {||oFormMain:lBmpCenter := .t.}
Called from source\winapi\hwindow.prg->HMAINWINDOW:NEW(271)
Error BASE/1005 Nenhuma vari vel exportada: LBMPCENTER
Called from ->_LBMPCENTER(0)
Works fine with 2.17
Best regards,
Itamar M. Lins Jr.
|
|
From: Itamar M. L. J. L. <ita...@gm...> - 2013-06-27 13:08:00
|
Hi!
Not found clausules of dialog GUILIB.CH
[ COLOR <clr> ]
[ <lnoClosable: NOCLOSABLE> ]
Error E0030 Syntax error "syntax error at 'DIALOG'"
Saudações,
Itamar M. Lins Jr.
|
|
From: oleksa <m.o...@uk...> - 2013-06-27 06:05:44
|
--- Оригінальне повідомлення --- Від кого: "Alexander S.Kresin" <al...@be...> Дата: 27 червня 2013, 08:15:16 > I still didn't understand, does the yesterday's fix : > > 2013-06-26 16:38 UTC+0300 Alexander Kresin <al...@be...> > * source/winapi/hcwindow.prg > * hwg_IsptrEq() instead of comparison of handles ( == ) > > solve the problem ? > > Regards, Alexander. > Yes, all ok now, thanks. Regards, Alexey Myronenko |
|
From: Alexander S.K. <al...@be...> - 2013-06-27 05:15:11
|
>> Such kind of operation on pointers ( == ) works in Harbour. Maybe you
>> migrated to xHarbour :) ? Or, maybe, something changed in Harbour ( I
>> use, as usually, not a latest version ).
>> Anyway, I replaced it by the hwg_isPtrEq(). Please, try now.
>>
> Now i'm use Version: Harbour 3.2.0dev (r1306101459), xHarbour never, only for some test. Maybe Przemyslaw can explain this problem with pointers.
>> Regards, Alexander.
>>
I still didn't understand, does the yesterday's fix :
2013-06-26 16:38 UTC+0300 Alexander Kresin <al...@be...>
* source/winapi/hcwindow.prg
* hwg_IsptrEq() instead of comparison of handles ( == )
solve the problem ?
Regards, Alexander.
|
|
From: Itamar M. L. J. L. <ita...@gm...> - 2013-06-26 15:52:52
|
@ 05,40 Browse oBrw DataBase ;
ON RIGHTCLICK {|This,nLine,nCol| ClickEsquerdo(This,nLine,nCol) }
Error E0030 Syntax error "syntax error at '{'"
Ps. My falt ButtonEx not include #include "hwg_extctrl.ch"
Becose emails of group developer no show here :(
Tks for fix of all problems until here!
Best regards,
Itamar M. Lins Jr.
|