Hi Pritpal,
GTWVG IMO still needs heavy development to be used
in production environments, as I can make it crash and
behave strangely in just a few seconds of regular clicking.
I am interested in your findings.
GTWVG is in use with my production applns well over few years
and I have not heard anything "crashing with clicks" so far.
Can you please enlighten me how it can be reproduced?
I would like it to be perfect in all senses.
Well, I was just clicking pretty randomly on the
windows/buttons and menus, and it was for one very
difficult to decide which window is active, and
I also couldn't really find out which window would
cause the app to close, and which would close the
window only, and what window will I end up with
after doing any of these. I didn't experience crash
this time.
It's difficult to tell which menu will open something,
and which button or toolbar icon will work or not work.
There are some browser separator line refresh problems,
but that's minor.
Maybe some 64-bit testing could be good with this code,
to see if it's indeed portable.
I've also mentioned once the bad refresh problems
when you have multiple windows open, moving the
foreground window, or closing one can leave non-updated
patches (sometimes black, sometimes just clearing
specific parts of the underlying objects, like the
filling of the circle / rectangle on the first dialog)
on the background window. I've seen a dialog appear
in black right after it appeared.
Overall for me the demo is a bit confusing as a GUI
app, this may be because this is just a demo app,
but the most worrying are the visual glitches.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
