FiveTech Software tech support forums

Silvio.Falconi

... comment, but not directly in the code.

Pix2Inch - Uses nXoffset and nYoffset in the comment, but not directly in the code.

// Set the X and Y offsets for printing
oPrn:nXoffset := 10; // Set X offset to 10 units
oPrn:nYoffset := 20; // Set Y offset to 20 units

// Now, when you print something ...

Otto

... comment, but not directly in the code.

Pix2Inch - Uses nXoffset and nYoffset in the comment, but not directly in the code.

// Set the X and Y offsets for printing
oPrn:nXoffset := 10; // Set X offset to 10 units
oPrn:nYoffset := 20; // Set Y offset to 20 units

// Now, when you print something ...

Silvio.Falconi

can i have an example how to print with class tprinter with offsets x and offsety ' ?

russimicro

... by another user.
This error can also occur when using the Advantage proprietary table type (ADTs) and the current record has been deleted.

Linux Note If using a pre-2.4 kernel, it is possible to get this error because of an incorrect lock offset range. See USE_LOW_LOCK_OFFSETS for more details.

bpd2000

... added support for large index files over 4GB length.
These are slightly modified CDX indexes which stores index page numbers
instead of index page offsets inside index file. This trick increase
maximum index files size from 2^32 (4GB) to 2^41 (2TB). This index
format is enabled automatically when DB ...

Rick Lipkin

... As you can see .. I added msginfo() to test the values and rem'd them out. Feel free to try them for yourselves. Please note that this code offsets the data by one character at the beginning and you may need to adjust the width of your variables.

Rick Lipkin

//------------------------Func ...

Gale FORd

... allowing the table to grow beyond the 2GB limit of the FoxPro driver. Advantage does this by using a 64-bit unsigned integer to calculate the file offsets, while VFP uses a 32-bit signed integer. Using a larger value to track the file offsets allows Advantage to access DBF files that exceed 2GB in ...

Bayron,

This is the line that makes the difference:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">

Anyhow, it partially gets IE working (menu is fine but dialogs offsets need to be fixed) and break Chrome...

James Bott

... vertical and horizontal "offset." These are the sections of the page along the borders that the printer cannot print on. Like resolution, these offsets may be different for each printer.

I forgot to include these offsets in my calculations. However, you can use the built in method in TPrinter ...

Davide,

> Why the offsets should be considered only if Preview is disabled ?

We implemented the Method ImportWMF() for a FWH user that needed it. Probably in his case it was required as he was satisfied with the results.

We can modify that code, no problem.

Davide

... if ! ::lMeta
SetViewOrg( ::hDCOut, -::nXoffset, -::nYoffset )
endif
By commenting those lines, the problem gets cured, but it seems to be intentional.

Why the offsets should be considered only if Preview is disabled ?
Antonio ?

Hi,
Davide

Richard Chidiak

... have to specify the size of the browse to make it work

@ 10,200 XBROWSE oBrw ;
OF wnd ;
SIZE ownd:nwidth - 200,ownd:nHeight - 30 PIXEL ;
ALIAS myalias

This syntax will work , if the size clauses is removed the browse will display but no offsets will be taken into consideration.

Rihard

... from the printable area. I'm not sure that the offset values need to be used anywhere since printable area already takes in to account the offsets.

No, it is correct. Without offset being subtracted, if you were print at 0 cm you would really print at the left printable margin that is not ...

James Bott

... nVertSize() ) - ::nYoffset )
nCol := Max( 0, ( nCol * 10 * ::nHorzRes() / ::nHorzSize() ) - ::nXoffset )

Because the offset is being subtracted from the printable area. I'm not sure that the offset values need to be used anywhere since printable area already takes in to account the offsets.

James

James Bott

Ramesh,

I find that often print drivers are inaccurate. They don't report the proper values for width, height, and x and y offsets (non-printable areas). So first I would check these.

oPrn:nXOffset
oPrn:nYOffset

Also check:
oPrn:nVertSize()
oPrn:nHorzSize()
oPrn:nVertRes()
oPrn:nHorzRes()

To see ...

FiveTech Software tech support forums

Search found 17 matches: offsets

Re: nYoffset and nXoffset

Re: nYoffset and nXoffset

offset

Re: ADSCDX/5035 The requested lock culd not be guaranted.

Re: File Size and Record Limit

Re: encrypting dbf files

Re: Converting CVS files

Re: FiveWin Web Interface

Re: What's the right technique using oPrn:SayBitmap()?

Corel.PRG - EMF bug - Solved (perhaps)