On Fri, Dec 12, 2008 at 8:23 PM, Pritpal Bedi wrote:
> Now with the extensive usage this GT has attracted in importance demands
> it to be extended to honor Windows protocols.
> ...
> I need group decision before proceeding to implement it.
IMHO GT has first of all to be 100% compatible with C5x
My choice is break with harbour 1.0 compatibility (but not break with
clip52 compatibility) for having a better approachWith scroll bar also
windows mobile will be possible!
2008/12/12 Pritpal Bedi
>
> Lorenzo and All,
>
>
> Lorenzo Fiorini-2 wrote:
> >
> > Many thanks, I've tried many change
Lorenzo and All,
Lorenzo Fiorini-2 wrote:
>
> Many thanks, I've tried many changes but I don't want to break other
> features ( like gtwvg ).
>
> IMHO the 1.0 way of working is more "clean".
> The "key" parameter has to be the font size since I may need a lot of
> rows and columns in a small w
On Fri, Dec 12, 2008 at 4:57 PM, Pritpal Bedi wrote:
> Me too is wondering what did change this behavior.
>
> I will try to resolve it by this weekend.
Many thanks, I've tried many changes but I don't want to break other
features ( like gtwvg ).
IMHO the 1.0 way of working is more "clean".
The
Lorenzo
Me too is wondering what did change this behavior.
I will try to resolve it by this weekend.
Regards
Pritpal Bedi
Lorenzo Fiorini-2 wrote:
>
> I'm trying to understand how to "fix" gtwvt in 1.1 but the problem
> seems "of design".
> What I mean is that gtwvt 1.1 seems to use always t
I'm trying to understand how to "fix" gtwvt in 1.1 but the problem
seems "of design".
What I mean is that gtwvt 1.1 seems to use always the row, col and
then find the best font size.
In this way "hard" to define a given font of a given size and for example
seems impossible to use the font "Terminal
