Please don't mix GTWVT and GTWVG together, they are
completely different GTs.
Misconception. This is partially true.
GTWVG is superset of GTWVT with some GUI constructs only.
If you do not call any GUI stuff, GTWVG is exactly like GTWVT.
Both GTs can be used interchangebly untill you call GUI stuff.
It's not exactly the same as it uses a slightly
different codebase, where full GTWVT implementation
is present in a modified form. Syncing is manual.
Plus of course the extra stuff, which doesn't
conform with quite some Harbour core standard.
AND there is NO MT issue with GTWVG.
My flagship production application "Vouch" ( extremely large )
running on 100s of clients is a pure GTWVG - MT - GUI application
and is running flawlessly. Look at Przemek's message in this context.
My only point was that mentioning "GTWVT/GTWVG"
as one entity is vague and may wash together
a contrib with a core component with different
codebases.
From such reports it's impossible to know whether
poster used both name by mistake, in fact you can't
be sure whether he's just confusing the two, and
which one he's using in reality. It's also impossible
to tell whether user refers to "extended" GTWVG
functionality or plain base GT one.
It turns out in this specific case it doesn't
matter, but generally speaking they are not the
same thing, and such vague reports can just ignite
other misconceptions and wrong ideas about Harbour.
Saying "doesn't support MT" for a core Harbour
component is a heavy claim, so we should avoid
being vague by all means in such case.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
