Will the Console Compiler compile programs that can run full screen in Vista?

[Guest]

And if so, does that include both 32-bit and 64-bit Vista systems? Also, I do mean run without the need for other software or modifications to the display driver, etc.

Thanks

Pete

[Fred Buffington]

The quick answer is probably yes and no.

With the statements in PBcc probably not (except for graphic more later).

1 possibility is stk routine using api such as createwindowex. I am by no means
an expert in this area but there should be some examples of creating windows in pbcc.

Another possibility is contools/graphics add-ons from perfect sync. They may be able to make a full-screen display and are fairly easy to use. (great products).

A third possibility (mentioned before) and probably the easiest, is a graphic screen using the graphic commands. This should be fairly easy to make a full screen.

[Guy Dombrowski]

Vista Full Screen

Time to use my Graphic Console technique.
Il will work with Vista and Windows Seven

[Guest]

Thanks Fred,

I've been holding out to see when such an update would occur. In QuickBasic, you could force full screen with a graphics screen call but of course it fails in Vista. QB64 uses SDK and will run full screen in Vista 32 and 64-bit systems but it is still in development.

I can adjust the display properties well enough to get about an 80% window but the problem today is there are so many screen displays used plus the standard and wide-screen monitors it is hard to rely on any one fixed setting.

A more complicated way to work around this has been to use older Windows 98 or XP PIF files and convert them to .LNK files to control the display, such as running in 640 x 480 screen resolution, adjusting the fonts, etc.

Anyway, thanks for your reply and I hope someday PowerBasic will be able to adapt to the newer operating systems, not that I like Vista, I don't, but there is no going back unless we find a decent time machine app posted somewhere.

Pete

[Fred Buffington]

I don't think there is any adaption necessary. The tools are there and available. Both guy and I are 'Old QB45 programmers' so you might try his suggestion. Personally, for Full Screen apps I prefer pbdll/pbwin and they are not difficult in my opinion.

[Kev Peel]

Not a PB problem...

Anyway, thanks for your reply and I hope someday PowerBasic will be able to adapt to the newer operating systems, not that I like Vista, I don't, but there is no going back unless we find a decent time machine app posted somewhere

PB/CC works fine in Vista, so no further changes are necessary. The problem is you want something that is not possible due to Microsoft - it was they who decided to remove full screen console support in Vista (and future versions of Windows), probably due to the new DWM. If other compilers support full screen they are not using the console. If you are willing to drop the console (#CONSOLE OFF), then PB/CC can use a graphics window or SDK techniques to create a full screen interface. It is a relatively easy thing to do.

PS. Changing the display driver is a hack, I really wouldn't recommend it.

[Dennis Allman]

And if so, does that include both 32-bit and 64-bit Vista systems? Also, I do mean run without the need for other software or modifications to the display driver, etc.

Thanks

Pete

Personally I would prefer to keep the console in a windowed mode in my text mode apps and use a licensed version of the ShareWare Ddoc Print and Preview program I have for their printing, saving and viewing services over either LPRINT or XPRINT because Ddoc provides all these services without programming them and reinventing the wheel so to speak. For a game or other graphic based program using PBCC however it may be possible to make a full screen graphics window using the GRAPHICS commands.

Bob Zale should really consider purchasing the Ddoc program from its author (a fellow PowerBASIC Programmer, Don Dickenson if he will sell and adding it to the PowerBASIC family.

[Michael Mattias]

Bob Zale should really consider purchasing the Ddoc program from its author (a fellow PowerBASIC Programmer, Don Dickenson if he will sell and adding it to the PowerBASIC family.

Adopt ddoc P&P? Why, so it can compete with PB's natural children, XPRINT and GRAPHIC PRINT?

ddoc P&P was developed long before there was an XPRINT. It has served long and well. But fact of life is, there is little you can do with ddoc P&P you can't do with 'native' functions now. (and vice versa).

MCM

[Dennis Allman]

One of the Problems with XPRINT and GRAPHICS PRINT is that they work on Windows Only printers ONLY. (at least acording to the PowerBASIC CC help file) There are some people still using the old DOS printers under Windows. (particularly those still using Win9x systems). I think Ddoc still handles this siutuation pretty well and that is why I continue to use it. I also don't see using LPRINT without any graphics functionality as a viable option either. That means I would have to add another print option to my programs and add twice as much code to the option menu, and produce another program still using Ddoc to print the graphics part separately. Using Ddoc for both print and graphic functions I can cover all printers that might be used with the program, graphics and all with a single program and code base.

[Michael Mattias]

old DOS printers under Windows.... I think Ddoc still handles this siutuation pretty well

It does?

[Dennis Allman]

My experience with printers only goes to an old parrallel port Canon Bubble Jet printer that used BOTH DOS escape codes and the Windows GDI with a proprietary driver. It worked with BOTH LPRINT and Ddoc Print and Preview and an Epson late model Parrallel port dot matrix that did likewise on the Windows GDI alone, (no proprietary driver). I dont know about earlier DOS printers.