Hi Przemek,
I think Pritpal is trying to get into the scheme of "inherits from
GTWVT
to avoid duplicated code".
IMO this way it's done the wrong way.
For one, GTWVG has - from the beginning -
lots of duplicated GTWVT code, which is
still there.
And Pritpal wants to remove it and simply in
Hi Pritpal, Przemek,
> I guess you want to create nested windows and you need parent window
> handle. Fine but what protection do you plan to make against destroying
> parent window with subwindow active? Can you define some expected
> behavior for such situation? What is real MS-window behavior i
Przemek
<<<
Conditional compilation does not resolve all problems and in some
situation it may not be enough. We should always try to reduce
and differences when possible.
>>>
ok.
<<<
>HB_GTI_WINDOWSTYLE
>HB_GTI_WINDOWEXSTYLE
Why do you need both?
I know CreateWindowEx() parameters but
On Wed, 29 Oct 2008, Pritpal Bedi wrote:
Hi Pritpal,
> You never have to look back which GT you are using. You have a feature or
> not can be
> controlled via a single define. I used this mechanism when working with
> Xbase++ and Clipper
> with same sources.
Conditional compilation does not re
Hello Przemek
<<<
And Pritpal wants to remove it and simply inherit from GTWVT.
IMHO it's good idea.
>>>
Exactly.
GTWVG is 100%GTWVT + Redirecting few more messages and extending the
structure a little bit.
GUI calls and elements are totally independant from core GTWVG.
So instead of updating G
After sending the following message I read Przemek's explanation which answers
all my
questions. Sorry for the noise...
regards,
budyanto
On 29 Oct 2008 at 23:43, "Harbour Project Main Develop wrote:
> Hi Viktor,
>
> Thanks for your explanation. There're still some things to clarify, if you
>
Hi Viktor,
Thanks for your explanation. There're still some things to clarify, if you
don't mind.
On 29 Oct 2008 at 7:50, Szakáts Viktor wrote:
> >> You're again and again trying to add Windows
> >> specific features to GTWVT, but such things
> >> simply don't belong there. GTWVT is a console
>
On Wed, 29 Oct 2008, Szak�ts Viktor wrote:
Hi Viktor and Pritpal,
>> I think Pritpal is trying to get into the scheme of "inherits from GTWVT
>> to avoid duplicated code".
> IMO this way it's done the wrong way.
> For one, GTWVG has - from the beginning -
> lots of duplicated GTWVT code, which i
Hi Budyanto,
On 2008.10.29., at 4:21, Budyanto Dj. wrote:
Hi Viktor,
On 28 Oct 2008 at 21:27, Szakáts Viktor wrote:
But why do you need to add all these non console
related stuff to GTWVT??
I think Pritpal is trying to get into the scheme of "inherits from
GTWVT to avoid duplicated code".
Hi Viktor,
On 28 Oct 2008 at 21:27, Szakáts Viktor wrote:
> But why do you need to add all these non console
> related stuff to GTWVT??
I think Pritpal is trying to get into the scheme of "inherits from GTWVT to
avoid duplicated code".
> You're again and again trying to add Windows
> specific f
Hi Pritpal,
Thanks for the ground work. I will do the rest.
I plan to introduce:
typedef struct
{
DWORD dwExStyle,/* 0 */
DWORD dwStyle, /* WS_THICKFRAME|WS_OVERLAPPED|WS_CAPTION|
WS_SYSMENU|WS_MINIMIZEBOX|WS_MAXIMIZEBOX */
intx, /* 0 */
int
Przemek
Przemyslaw Czerpak-2 wrote:
>
> 2008-10-28 12:53 UTC+0100 Przemyslaw Czerpak (druzus/at/priv.onet.pl)
> * harbour/source/rtl/gtwvt/gtwvt.h
> * harbour/source/rtl/gtwvt/gtwvt.c
> + added support for creating console window after 1-st screen update
> Please remember that it
2008-10-28 12:53 UTC+0100 Przemyslaw Czerpak (druzus/at/priv.onet.pl)
* harbour/source/rtl/gtwvt/gtwvt.h
* harbour/source/rtl/gtwvt/gtwvt.c
+ added support for creating console window after 1-st screen update
Please remember that it interacts with inkey() code which does not
wor
13 matches
Mail list logo
