On Tue, 06 Oct 2009, Szak�ts Viktor wrote:
Just tested MSVC 2008 x86 now default UNICODE build
and I'm having the same display problems in GTWIN
as in x64.
As it turns out, it's not related to UNICODE build
though. The console app was starting up with default
screen dimensions which is 80x300, and apparently
this messes it up. I'll have to investigate further
how can any screen dimension mess up such things
as windows handling. [ and now Windows doesn't seem
to allow me to reset the value to original defaults,
well, time to go anyway. ]
It's expected behavior. In Win2K and higher the size of console
buffer is returned as window size. If you do not need such big
area then simply change to size of console buffer in application
preferences or use setMode()
I know this. I need to clarify, by "messed up" I don't
mean the scrollbars and whatnot when using such big
buffer. Instead I mean that the displayed (by Harbour
app) _screen content_ is wrong. It looks like as if
(ctwin) windowing gets confused about current window,
so it's painting to the wrong one and returning size of
the wrong one. But I'll make some real tests later,
could be my app code.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
