Hi Pritpal,
> I tried but am unable to use it in a generic way. May be
> I am not familiar with this concept since begining.
> Francesco was trying to make it generic, so I am waiting
> till he comes up with this solution. I, at my level best, can do
> with which I am familiar.
Thanks, I think you should look at it, the other thing is GC
collected pointers which is essential for a lot of tasks here.
I'd suggest to try it, it's not that bad believe me.
> I could not follow what you mean. Can you explain which
> part of GTWVG is not upto Harbour standards or I am
> missing something? Please explain it in detail. We can
> follow the right direction, no compulsions.
1) You're introducing xhb dependency for gtwvg, which isn't good.
2) Problem reports of gtwvg problems are ignored.
3) Instead of moving useful and existing WAPI functionality from
existing libs to hbwin, you're adding plain new ones.
Which is by itself not a problem, currently messes situation
just gets even more messed by growing another branch
here without touching the numerous existing ones.
As a final effect it seems that we're growing another hbwhat
lib, and not getting closer to a well laid and unified Windows
interface.
At least, that's how it looks from here so far.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
