Hi Przemek,
The main problem for me is that I do not use Windows
and I do not know well MS-Windows API and undocumented
behavior. Working on GTWVT I'm making tests with WINE
but I'm never sure when I want to check some detail
behavior which is not documented that I see real MS-Windows
results or only WINE emulation side effects.
Here to well redesign GTWVT internals I should make some
tests on real MS-Windows machine to be sure that I choose
correct implementation.
I see, difficult to add anything smart to this,
native is always better than emulation. Dunno where
WINE stands these days really.
I know it's not ideal, but if you want I can give
you remote access to Windows (virtual) PC, if that may
help you in any ways. Just tell.
Another remaining issue is screen refresh problem, which
should probably put in a separate native thread as you've
suggested already. Maybe this would solve some bad refresh
problems in GTWVG, too.
I cannot promise but I'll try to find some time to implement it.
Okay, that would be very nice.
from being a priority (for me) as I don't have long
queues of Linux/OSX users in front of my door :) (yet :)
Please remember that in some GTs we are not able to protect
against terminal resizing from Harbour application so such
situations will always happen and support for dynamic font
resizing is rather seldom and will exist only in GUI GTs.
Disabling resize is not really the problem, and it isn't
nice to do that with the users anyway. Rather, resizing can
either resize the screen dimension or the font size. Now GTXWC
is doing the former, while GTWVT does the latter (by default).
Latter is more natural for legacy CUI apps, former leads
to bad results without heavy app rewrite usually.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
