nto di Pritpal Bedi
> Inviato: domenica 28 febbraio 2010 22.15
> A: harbour@harbour-project.org
> Oggetto: Re: R: [Harbour] Re: gtwvt compatibility issue
>
>
>
> Viktor Szakáts wrote:
> >
> >> Anyway, having a GTQTC working could be a good bridge to
> port grad
Da: harbour-boun...@harbour-project.org
> [mailto:harbour-boun...@harbour-project.org] Per conto di
> Viktor Szakáts
> Inviato: domenica 28 febbraio 2010 21.16
> A: Harbour Project Main Developer List.
> Oggetto: Re: R: [Harbour] Re: gtwvt compatibility issue
>
> > Anyway
Viktor Szakáts wrote:
>
>> Anyway, having a GTQTC working could be a good bridge to port gradually a
>> console application to hbqt, as Pritpal could allow the cohexistence of
>> the
>> two libs.
>> I'm interested about the thought of Viktor and Pritpal about this.
>
> IMO we should first try i
> Anyway, having a GTQTC working could be a good bridge to port gradually a
> console application to hbqt, as Pritpal could allow the cohexistence of the
> two libs.
> I'm interested about the thought of Viktor and Pritpal about this.
IMO we should first try if it's possible to create mixed
GTWVT/
rbour-boun...@harbour-project.org
[mailto:harbour-boun...@harbour-project.org] Per conto di Viktor Szakáts
Inviato: domenica 28 febbraio 2010 16.27
A: Harbour Project Main Developer List.
Oggetto: Re: R: [Harbour] Re: gtwvt compatibility issue
Maurizio la Cecilia wrote:
>
> a build with GTQT
Viktor Szakáts wrote:
>
>> I will do after hbIDE reaches an acceptable stage.
>
> IMO we (well, you) should focus on making QT stable.
>
> F.e. I'm still getting the crash at program exit, and
> without wanting to go into it deeply, for me most
> menu functionality seemed broken. F.e. open fil
>> Nothing changed AFAIK. Accented / non-ASCII chars
>> never worked alright and there were several other screen
>> artifact, performance was very slow and there were
>> several basic problems with it (f.e. screen marking feature
>> mixed up with mouse/key input). I reported some of
>> these long a
Viktor Szakáts wrote:
>
> Nothing changed AFAIK. Accented / non-ASCII chars
> never worked alright and there were several other screen
> artifact, performance was very slow and there were
> several basic problems with it (f.e. screen marking feature
> mixed up with mouse/key input). I reported s
>
> Maurizio la Cecilia wrote:
> >
> > a build with GTQTC showed me that the colors
> > don't are coded in Clipper compatibility mode (as Viktor recent changed
> on
> > WVT) and, mainly, many codepage and save/restscreen() problems.
> > The box graphics and localized character, and the colors of
>
Maurizio la Cecilia wrote:
>
> a build with GTQTC showed me that the colors
> don't are coded in Clipper compatibility mode (as Viktor recent changed on
> WVT) and, mainly, many codepage and save/restscreen() problems.
> The box graphics and localized character, and the colors of saved/restored
Not only GTWVG needs an update: a build with GTQTC showed me that the colors
don't are coded in Clipper compatibility mode (as Viktor recent changed on
WVT) and, mainly, many codepage and save/restscreen() problems.
The box graphics and localized character, and the colors of saved/restored
areas ar
11 matches
Mail list logo
