Hi Viktor,
>Theoretically yes. It's difficult to tell, since I
>don't have xhb (and parts) running here, but the RDD
>model is exactly the same in both projects.
I'll try to use it and I'll tell my findings (But as I know they change some
low level API of RDD in xHarbour). But I don't know if I violate my contract
with "xHarbour.com". Maybe Przemek knows better.
>Okay, I begin to understand. Looking at the 500KB large
>source file, it's not easy to find out anything :)
>If it's what I think, it could be quite useful. I just
>wonder what does take so much source code... Probably those
>Windows parts. Which BTW I think would be better added
>differently so that the whole GT doesn't get tied to
>the Windows platform.
A lot of source code inside GTWVW does nothing. As an example look at this
#ifndef _WIN32_IE
#define _WIN32_IE 0x0400
#endif
And later #if _WIN32_IE > 0x400
>How do you see it, are there any chances this GT
>will be updated to the new GT model? (now also used
>in xhb)
To be truth I don't know. I'm a clipper and .Net programmer and I've made
only small changes to GTWVW. I had a contract with a C programmer for the
scale font changes. But I'm ready to pay for such a conversion. What I
believe as the best way is a low level api (something like the new GT API
but with new additions). Later must be another level with common
windows-linux (GUI-CUI) support. And a third level specific to each GT. Of
course I'm not the one that can design something like that.
This are some screenshots but they are big from 1 to 3.5 MB.
http://prosvasis.vivodinet.gr/download/temp/dos.bmp
http://prosvasis.vivodinet.gr/download/temp/resized.bmp
http://prosvasis.vivodinet.gr/download/temp/u1.bmp
http://prosvasis.vivodinet.gr/download/temp/u2.bmp
Brgds,
Mike
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
