Printers, Printers, Printers...

Post by **Antonio Linares** » Tue Dec 05, 2006 4:39 am

Gilbert, Badara,

>
I`m saying that DevMode(), DeviceCaps() and GetDeviceCaps() are resulting erroneaus results.
>

Could you please provide us a small sample to reproduce the errors ? Thanks,

>
I have exactly the same problem with this functions Gilbert,
since the day i have purchased FW 2.5 and FWH 2.5.
I have reported these bugs to Antonio there is o long time,
nobody do nothing to solve this.
>

Sometimes we miss a tech support requirement. On those ocassions, PLEASE insist to get a fix from us. Thanks,

Badara Thiam · Post by **Badara Thiam** » Wed Dec 06, 2006 10:58 pm

Gilbert,

mais si tu me laisse ton E-Mail je te ferai parvenir l`information

Je t'ai transmis un message privé, l'as-tu reçu ?

Regards,

Badara Thiam · Post by **Badara Thiam** » Wed Dec 06, 2006 11:10 pm

Antonio,

It is easy to see DeviceCapa() don't work, like DevMode()
and some others printing functions, and TPrinter() originale class,
with the FW 2.5 pack.

Regards,

Post by **Antonio Linares** » Thu Dec 07, 2006 1:16 am

Badara,

> It is easy to see DeviceCapa() don't work, like DevMode()

If it is so easy, then please provide a small sample, thanks

Ken Wantz · Post by **Ken Wantz** » Thu Dec 07, 2006 1:39 am

If you are using FW why not give PageScript 4 a try or PageScript32 if you are using xHarbour. There are demo versions for both. I used Pagescript 4 for the past year and the only trouble being printing patterns to a LJ 4 printer. Not sure if the pattern problem exists with PageScript32.

A couple of problems I did have were resolved within less than 2 days. I am just starting to get acquainted with the FW demo so I am not sure if will be any compatibility problems with PageScript. One change I had to make was to alter the .ini in PageScript 4 or use PSSetUseDIB(.F.) in PageScript32 or I could not print images to a LJ 4 printer properly.

Suggest you give PageScript a try. The site is www.abeelabs.com. It is located in Quebec so any questions you have can be asked in French.

Good Luck,

Ken

Badara Thiam · Post by **Badara Thiam** » Thu Dec 07, 2006 8:52 am

Ken,

PageScript 4 not work with Clipper Windows programs.
Just for DOS Clipper. In the release i have. I use it since
few years in my DOS Clipper programs.

I have rewritted all Pagescript functions i need,
to work in the same way under Windows programs.

I will see the last upgrades.
Thank you for the information.

Regards,

Badara Thiam · Post by **Badara Thiam** » Thu Dec 07, 2006 8:56 am

Antonio Linares wrote:Badara,

> It is easy to see DeviceCapa() don't work, like DevMode()

If it is so easy, then please provide a small sample, thanks

To test, insert DeviceCapa() in your main PRG and test compile
with FW 2.5 (october 2004). You see like me, or you have not
the same FW 2.5 pack.

Do the same with DevMode().

Regards,

Ken Wantz · Post by **Ken Wantz** » Thu Dec 07, 2006 3:39 pm

Badara,

In this highly technical world it is very easy to misinterpret what is meant or said.

First, you are correct in saying that PageScript 4, currently at version 4.1.0, only works with DOS Clipper. If FW, the DOS Clipper version were added, the combination would work with DOS Clipper.

Second, Stephan has stated many times that PageScript 4 could not be used with 32 bit programs and no 32 bit version was available. A couple of months ago AbeeLabs finally released PageScript32 version 1.0 which does work with 32 bit programs. The package contains all files needed to work with xHarbour, Xbase++ or Delphi.

One change is needed to migrate to xHarbour if PSTextOut() was used rather than Textout. In that case, one line is added for PageScript 4 compatibility.

I am still looking at the FW demo. There are several things I do now in Clipper that I need to learn how to do before I purchase FWH.

Neither FiveWin or xHarbour offer patches for older versions; you must either upgrade or subscribe. It may be that version 2.8 has fixed Gilbert's and your particular problems.

The solution to a post where a person with a problem in 2.7 was to purchase an upgrade. I wonder if the currently acknowledged problems in 2.8 will not get fixed until 2.9.

Bugs in the software should not require a user to pay for an upgrade to get the fix. There should be a limit on the time a version is supported but should exist in some form. The next version may contain a whole new set of bugs! Could this be a carefully designed plot???

Regards,

Ken

Post by **Antonio Linares** » Thu Dec 07, 2006 5:23 pm

Ken,

All bugs fixes are published on these forums for free. We don't ask money for fixes. But users miss to apply them or simply work with very old versions and/or modified versions by themselves.

On such scenario, only upgrading is the way to guarantie that they use the right software build.

Besides that, when you buy a product from us you get two months of free upgrades.

Post by **Antonio Linares** » Thu Dec 07, 2006 5:25 pm

Badara Thiam wrote:
Antonio Linares wrote:Badara,

> It is easy to see DeviceCapa() don't work, like DevMode()

If it is so easy, then please provide a small sample, thanks
To test, insert DeviceCapa() in your main PRG and test compile
with FW 2.5 (october 2004). You see like me, or you have not
the same FW 2.5 pack.

Do the same with DevMode().

Please provide a small and self contained sample. The functions that you mention require parameters, what parameters are you using ? You need to provide us enough feedback so we can provide you the right tech support, thanks.

James Bott · Post by **James Bott** » Thu Dec 07, 2006 5:35 pm

I remember reading somewhere that DeviceCaps() and DevMode() don't even work the same on different OSs, so this may be a Windows problem not a FWH issue. You might try Googling them to see what you can find.

James

Badara Thiam · Post by **Badara Thiam** » Fri Dec 08, 2006 1:51 pm

James,

Thanks, but i have this book (Editor SAMS) :
Microsoft Windows 2000 API SuperBible

And he say DeviceCapabilities() work under
Windows 98 and 2000. No restrictions.