I migrated a Clipper application to XBase. No problem so far. The Clipper 
version could be expanded over the whole screen. It used a pif (DOS, program 
information file) for the specifications of the screen size and the used 
font. Now the XBase application is just shown in a small window. It doesn't 
have to be full screen, but now it's too small to work with.

Is there any simple method to define the XBase window dynamic, so every 
single user can adjust the screen size to it's own needs?

M.vr.gr.,
Gert

hi,

> I migrated a Clipper application to XBase. No problem so far. The Clipper 
> version could be expanded over the whole screen. It used a pif (DOS, 
> program information file) for the specifications of the screen size and 
> the used font.

read about APPSYS and vCRT

> Now the XBase application is just shown in a small window. It doesn't 
> have to be full screen, but now it's too small to work with.

There is not "full Screen" for W32 Application ! only "maximize"

default Hybrid font is "Alaska CRT" and default Fontsize = 10
so you will get a 640x480 Window. to "fill" a 1024x768 Screen i use

*** quote ***
            
             create CRT 43x126
            
            oCrt := XbpCrt() :new( oStatic,, { 0,0 }, 43, 126 )
            oCrt:move := { | aPos, x, obj | obj:SetPos( { 0, 0 } ) }
            
             set Font Type and Size
            
            oCrt:FontName := "Alaska Crt"
            oCrt:FontHeight := 16
            oCrt:FontWidth  := 8

            oCrt:autoFocus := .T.
            oCrt:autoMark  := .T.
            oCrt:setName( ID_CRT1 )
            oCrt:create()

           SetAppWindow( oCrt )

*** eof ***

> Is there any simple method to define the XBase window dynamic, so every 
> single user can adjust the screen size to it's own needs?

switch to GUI 

it does not make Sence for a Hybrid Window.
depending on your Graficcard you can get 25/30/43 or 50 Lines,
while other might not "fit".

greetings by OHR
Jimmy

Hi

i use lucida console then

            oCrt:FontName := "Lucida Console"
            oCrt:FontHeight := 16
            oCrt:FontWidth  := 8

where
if you use 80col x 25 row
your resolution = { ( oCrt:FontHeight  * 25 ) * ( oCrt:FontWidth * 80 ) }
it must be <= setappwindow():currentsize()

regards

"AUGE_OHR" <AUGE_OHR*AT*WEB.DE> escribió en el mensaje de noticias 
news:676bb039$6f079aa3$3ee2@news.alaska-software.com...
> hi,
>
>> I migrated a Clipper application to XBase. No problem so far. The Clipper 
>> version could be expanded over the whole screen. It used a pif (DOS, 
>> program information file) for the specifications of the screen size and 
>> the used font.
>
> read about APPSYS and vCRT
>
>> Now the XBase application is just shown in a small window. It doesn't 
>> have to be full screen, but now it's too small to work with.
>
> There is not "full Screen" for W32 Application ! only "maximize"
>
> default Hybrid font is "Alaska CRT" and default Fontsize = 10
> so you will get a 640x480 Window. to "fill" a 1024x768 Screen i use
>
> *** quote ***
>            
>             create CRT 43x126
>            
>            oCrt := XbpCrt() :new( oStatic,, { 0,0 }, 43, 126 )
>            oCrt:move := { | aPos, x, obj | obj:SetPos( { 0, 0 } ) }
>            
>             set Font Type and Size
>            
>            oCrt:FontName := "Alaska Crt"
>            oCrt:FontHeight := 16
>            oCrt:FontWidth  := 8
>
>            oCrt:autoFocus := .T.
>            oCrt:autoMark  := .T.
>            oCrt:setName( ID_CRT1 )
>            oCrt:create()
>
>           SetAppWindow( oCrt )
>
> *** eof ***
>
>> Is there any simple method to define the XBase window dynamic, so every 
>> single user can adjust the screen size to it's own needs?
>
> switch to GUI 
>
> it does not make Sence for a Hybrid Window.
> depending on your Graficcard you can get 25/30/43 or 50 Lines,
> while other might not "fit".
>
> greetings by OHR
> Jimmy
>

On Thu, 23 Apr 2009 13:19:05 +0200, "Gert van der Wouden"
<gwouden@planet.nl> wrote:

>I migrated a Clipper application to XBase. No problem so far. The Clipper 
>version could be expanded over the whole screen. It used a pif (DOS, program 
>information file) for the specifications of the screen size and the used 
>font. Now the XBase application is just shown in a small window. It doesn't 
>have to be full screen, but now it's too small to work with.
>
>Is there any simple method to define the XBase window dynamic, so every 
>single user can adjust the screen size to it's own needs?


>> Is there any simple method to define the XBase window dynamic, so every 
>> single user can adjust the screen size to it's own needs?

>switch to GUI 

>it does not make Sence for a Hybrid Window.
>depending on your Graficcard you can get 25/30/43 or 50 Lines,
>while other might not "fit".

Jimmy is correct.  Here in this news group we have seen this same
story unfold over and over and over again, like an automatic re-run
tape.  In the long run the only truly satisfactory solution is to
convert to a full GUI app.  Many people over the past years here have
reported that they felt that the time and effort they put into
Crt/Hybrid apps was essentially wasted.  After exhaustive effort, time
and expense, they still were not fully satisfied and finally gave up
and went to GUI, and lamented that they didn't do it sooner.

So the generally best advice is to begin moving to pure GUI ASAP.
You'll be glad you did.


Regards,
Clayton

Clayton Jones   www.cjcom.net 
 Top-Down Library for Xbase++
 X-DBU Database Utility   
 X-MEMO Memo Field Replacement

From Clayton Jones:
> Jimmy is correct.  Here in this news group we have seen this same
> story unfold over and over and over again, like an automatic re-run
> tape.  In the long run the only truly satisfactory solution is to
> convert to a full GUI app.  Many people over the past years here have
> reported that they felt that the time and effort they put into
> Crt/Hybrid apps was essentially wasted.  After exhaustive effort, time
> and expense, they still were not fully satisfied and finally gave up
> and went to GUI, and lamented that they didn't do it sooner.
> 
> So the generally best advice is to begin moving to pure GUI ASAP.
> You'll be glad you did.

Hey, thats me.... I wasted 2 years for migration from clipper to
Crt/Hybrid app. It works, it even looks good - I use Clayton TopDown
libray for browse, menus ..., but the input form stil use xbpcrt window
dialog, so I use standard clipper syntay @ say .... & @ get
But .... this is not what customers wants, they want pure GUI.
So, please, dont make a same mistake as I do, move to GUI, please ...
( and buy some excelent lib, like TopDown or Expres)

I attach sample with Hybrid modul (TopDown graphics with XbpCrt window)

Miran Zupan
Slovenija

Thanks all for your comments.
GUI seems to be the only and right way to follow.

Regards, Gert

M.vr.gr.,
Gert
"Gert van der Wouden" <gwouden@planet.nl> schreef in bericht 
news:16dc7e58$26a73748$10ad@news.alaska-software.com...
>I migrated a Clipper application to XBase. No problem so far. The Clipper 
>version could be expanded over the whole screen. It used a pif (DOS, 
>program information file) for the specifications of the screen size and the 
>used font. Now the XBase application is just shown in a small window. It 
>doesn't have to be full screen, but now it's too small to work with.
>
> Is there any simple method to define the XBase window dynamic, so every 
> single user can adjust the screen size to it's own needs?
>
> -- 
>
>
> M.vr.gr.,
> Gert

Hello Geert,

There is a Dutch Xbase++ user group with several meetings a year.
Most (if not all) had the same problem.
There is more then 1 solution to migrate to GUI.
- Use Express++
- Use Top-down
- Use Formdesigner
- Build dialogs yourself.

The first and second options give the quickest result.

Personaly i use Express++. If you look at www.jdsoftware.nl, you find some 
screenshots of Xbase++ apps that have been converted from Clipper to GUI.

If you require more information on XXP, drop me a mail.

Regards,
Jack Duijf






"Gert van der Wouden" <gwouden@planet.nl> schreef in bericht 
news:16dc7e58$26a73748$10ad@news.alaska-software.com...
>I migrated a Clipper application to XBase. No problem so far. The Clipper 
>version could be expanded over the whole screen. It used a pif (DOS, 
>program information file) for the specifications of the screen size and the 
>used font. Now the XBase application is just shown in a small window. It 
>doesn't have to be full screen, but now it's too small to work with.
>
> Is there any simple method to define the XBase window dynamic, so every 
> single user can adjust the screen size to it's own needs?
>
> -- 
>
>
> M.vr.gr.,
> Gert

Hi Jack,

I downloaded the demo of Express++ from the Donnay site to have a look into 
it, but it will not run. It keeps complaining about a JACE31XP.dll that 
cannot be found. Copying the DLL from other directories gives memory 
problems.
I'm running Vista with XBase 1.90

Regards,
Gert van der Wouden

M.vr.gr.,
Gert
"Jack Duijf" schreef in bericht 
news:36b81b4b$5bcc44d0$805d@news.alaska-software.com...
> Hello Geert,
>
> There is a Dutch Xbase++ user group with several meetings a year.
> Most (if not all) had the same problem.
> There is more then 1 solution to migrate to GUI.
> - Use Express++
> - Use Top-down
> - Use Formdesigner
> - Build dialogs yourself.
>
> The first and second options give the quickest result.
>
> Personaly i use Express++. If you look at www.jdsoftware.nl, you find some 
> screenshots of Xbase++ apps that have been converted from Clipper to GUI.
>
> If you require more information on XXP, drop me a mail.
>
> Regards,
> Jack Duijf
>
>
>
>
>
>
> "Gert van der Wouden" <gwouden@planet.nl> schreef in bericht 
> news:16dc7e58$26a73748$10ad@news.alaska-software.com...
>>I migrated a Clipper application to XBase. No problem so far. The Clipper 
>>version could be expanded over the whole screen. It used a pif (DOS, 
>>program information file) for the specifications of the screen size and 
>>the used font. Now the XBase application is just shown in a small window. 
>>It doesn't have to be full screen, but now it's too small to work with.
>>
>> Is there any simple method to define the XBase window dynamic, so every 
>> single user can adjust the screen size to it's own needs?
>>
>> -- 
>>
>>
>> M.vr.gr.,
>> Gert
>
>
> __________ Informatie van ESET Smart Security, versie van database 
> viruskenmerken 4066 (20090512) __________
>
> Het bericht is gecontroleerd door  ESET Smart Security.
>
> http://www.eset.com
>
>
> 


__________ Informatie van ESET Smart Security, versie van database viruskenmerken 4066 (20090512) __________

Het bericht is gecontroleerd door  ESET Smart Security.

http://www.eset.com

Gert,

You may want to have a look at:
[XPPROOT]\xppw32\source\sys\appsys.prg

    CASE nAppType == APPTYPE_PM
       etc...

Regards,
Frans Vermeulen

> Hi Jack,
> 
> I downloaded the demo of Express++ from the Donnay site to have a look into 
> it, but it will not run. It keeps complaining about a JACE31XP.dll that 
> cannot be found. Copying the DLL from other directories gives memory 
> problems.
> I'm running Vista with XBase 1.90
> 
> Regards,
> Gert van der Wouden
> -- 
> 
> 
> M.vr.gr.,
> Gert
> "Jack Duijf" schreef in bericht 
> news:36b81b4b$5bcc44d0$805d@news.alaska-software.com...
> > Hello Geert,
> >
> > There is a Dutch Xbase++ user group with several meetings a year.
> > Most (if not all) had the same problem.
> > There is more then 1 solution to migrate to GUI.
> > - Use Express++
> > - Use Top-down
> > - Use Formdesigner
> > - Build dialogs yourself.
> >
> > The first and second options give the quickest result.
> >
> > Personaly i use Express++. If you look at www.jdsoftware.nl, you find some 
> > screenshots of Xbase++ apps that have been converted from Clipper to GUI.
> >
> > If you require more information on XXP, drop me a mail.
> >
> > Regards,
> > Jack Duijf
> >
> >
> >
> >
> >
> >
> > "Gert van der Wouden" <gwouden@planet.nl> schreef in bericht 
> > news:16dc7e58$26a73748$10ad@news.alaska-software.com...
> >>I migrated a Clipper application to XBase. No problem so far. The Clipper 
> >>version could be expanded over the whole screen. It used a pif (DOS, 
> >>program information file) for the specifications of the screen size and 
> >>the used font. Now the XBase application is just shown in a small window. 
> >>It doesn't have to be full screen, but now it's too small to work with.
> >>
> >> Is there any simple method to define the XBase window dynamic, so every 
> >> single user can adjust the screen size to it's own needs?
> >>
> >> -- 
> >>
> >>
> >> M.vr.gr.,
> >> Gert
> >
> >
> > __________ Informatie van ESET Smart Security, versie van database 
> > viruskenmerken 4066 (20090512) __________
> >
> > Het bericht is gecontroleerd door  ESET Smart Security.
> >
> > http://www.eset.com
> >
> >
> > 
> 
> 
> __________ Informatie van ESET Smart Security, versie van database viruskenmerken 4066 (20090512) __________
> 
> Het bericht is gecontroleerd door  ESET Smart Security.
> 
> http://www.eset.com
> 
> 
>

Frans,

this is exactly how I solved the problem. I found the solution in the 
knowledge base at the Alaska site.

But thnx anyway.

M.vr.gr.,
Gert
"Frans Vermeulen" <fransv@sluyter-1ogistics.nl> schreef in bericht 
news:20090512112030.4ce74628.fransv@sluyter-1ogistics.nl...
> Gert,
>
> You may want to have a look at:
> [XPPROOT]\xppw32\source\sys\appsys.prg
>
>    CASE nAppType == APPTYPE_PM
>       etc...
>
> Regards,
> Frans Vermeulen
>
>> Hi Jack,
>>
>> I downloaded the demo of Express++ from the Donnay site to have a look 
>> into
>> it, but it will not run. It keeps complaining about a JACE31XP.dll that
>> cannot be found. Copying the DLL from other directories gives memory
>> problems.
>> I'm running Vista with XBase 1.90
>>
>> Regards,
>> Gert van der Wouden
>> -- 
>>
>>
>> M.vr.gr.,
>> Gert
>> "Jack Duijf" schreef in bericht
>> news:36b81b4b$5bcc44d0$805d@news.alaska-software.com...
>> > Hello Geert,
>> >
>> > There is a Dutch Xbase++ user group with several meetings a year.
>> > Most (if not all) had the same problem.
>> > There is more then 1 solution to migrate to GUI.
>> > - Use Express++
>> > - Use Top-down
>> > - Use Formdesigner
>> > - Build dialogs yourself.
>> >
>> > The first and second options give the quickest result.
>> >
>> > Personaly i use Express++. If you look at www.jdsoftware.nl, you find 
>> > some
>> > screenshots of Xbase++ apps that have been converted from Clipper to 
>> > GUI.
>> >
>> > If you require more information on XXP, drop me a mail.
>> >
>> > Regards,
>> > Jack Duijf
>> >
>> >
>> >
>> >
>> >
>> >
>> > "Gert van der Wouden" <gwouden@planet.nl> schreef in bericht
>> > news:16dc7e58$26a73748$10ad@news.alaska-software.com...
>> >>I migrated a Clipper application to XBase. No problem so far. The 
>> >>Clipper
>> >>version could be expanded over the whole screen. It used a pif (DOS,
>> >>program information file) for the specifications of the screen size and
>> >>the used font. Now the XBase application is just shown in a small 
>> >>window.
>> >>It doesn't have to be full screen, but now it's too small to work with.
>> >>
>> >> Is there any simple method to define the XBase window dynamic, so 
>> >> every
>> >> single user can adjust the screen size to it's own needs?
>> >>
>> >> -- 
>> >>
>> >>
>> >> M.vr.gr.,
>> >> Gert
>> >
>> >
>> > __________ Informatie van ESET Smart Security, versie van database
>> > viruskenmerken 4066 (20090512) __________
>> >
>> > Het bericht is gecontroleerd door  ESET Smart Security.
>> >
>> > http://www.eset.com
>> >
>> >
>> >
>>
>>
>> __________ Informatie van ESET Smart Security, versie van database 
>> viruskenmerken 4066 (20090512) __________
>>
>> Het bericht is gecontroleerd door  ESET Smart Security.
>>
>> http://www.eset.com
>>
>>
>>
>
> __________ Informatie van ESET Smart Security, versie van database 
> viruskenmerken 4067 (20090512) __________
>
> Het bericht is gecontroleerd door  ESET Smart Security.
>
> http://www.eset.com
>
>
> 


__________ Informatie van ESET Smart Security, versie van database viruskenmerken 4070 (20090513) __________

Het bericht is gecontroleerd door  ESET Smart Security.

http://www.eset.com

Hallo Geert,

Recompile the code in \Express\sources\jazzage
This wil generate the requested dll.
Then you place this in the bin19 folder.

Regards,
Jack Duijf

"Gert van der Wouden" <gwouden@planet.nl> schreef in bericht 
news:1e830676$1e9d5b60$def6@news.alaska-software.com...
> Hi Jack,
>
> I downloaded the demo of Express++ from the Donnay site to have a look 
> into it, but it will not run. It keeps complaining about a JACE31XP.dll 
> that cannot be found. Copying the DLL from other directories gives memory 
> problems.
> I'm running Vista with XBase 1.90
>
> Regards,
> Gert van der Wouden
> -- 
>
>
> M.vr.gr.,
> Gert
> "Jack Duijf" schreef in bericht 
> news:36b81b4b$5bcc44d0$805d@news.alaska-software.com...
>> Hello Geert,
>>
>> There is a Dutch Xbase++ user group with several meetings a year.
>> Most (if not all) had the same problem.
>> There is more then 1 solution to migrate to GUI.
>> - Use Express++
>> - Use Top-down
>> - Use Formdesigner
>> - Build dialogs yourself.
>>
>> The first and second options give the quickest result.
>>
>> Personaly i use Express++. If you look at www.jdsoftware.nl, you find 
>> some screenshots of Xbase++ apps that have been converted from Clipper to 
>> GUI.
>>
>> If you require more information on XXP, drop me a mail.
>>
>> Regards,
>> Jack Duijf
>>
>>
>>
>>
>>
>>
>> "Gert van der Wouden" <gwouden@planet.nl> schreef in bericht 
>> news:16dc7e58$26a73748$10ad@news.alaska-software.com...
>>>I migrated a Clipper application to XBase. No problem so far. The Clipper 
>>>version could be expanded over the whole screen. It used a pif (DOS, 
>>>program information file) for the specifications of the screen size and 
>>>the used font. Now the XBase application is just shown in a small window. 
>>>It doesn't have to be full screen, but now it's too small to work with.
>>>
>>> Is there any simple method to define the XBase window dynamic, so every 
>>> single user can adjust the screen size to it's own needs?
>>>
>>> -- 
>>>
>>>
>>> M.vr.gr.,
>>> Gert
>>
>>
>> __________ Informatie van ESET Smart Security, versie van database 
>> viruskenmerken 4066 (20090512) __________
>>
>> Het bericht is gecontroleerd door  ESET Smart Security.
>>
>> http://www.eset.com
>>
>>
>>
>
>
> __________ Informatie van ESET Smart Security, versie van database 
> viruskenmerken 4066 (20090512) __________
>
> Het bericht is gecontroleerd door  ESET Smart Security.
>
> http://www.eset.com
>
>
>