here is my version of the Quicken wallet check definition. The principal change 
is to set the y-translation offset to 0.0. I also added a couple things to the 
stub and put the date and amount_number in better places for my low-end check 
source.

[Top]
Guid = 61d7469d-db2c-4842-bef9-8be7d4f5685e
Title = dbr Quicken(tm) Wallet Checks w/ side stub
Rotation = 0.0
Translation = 0.0;0.0
Show_Grid = false
Show_Boxes = false

[Check Positions]
Height = 204.0
Names = Top;Middle;Bottom

[Check Items]
Type_1 = PAYEE
Coords_1 = 231.0;61.0

Type_2 = AMOUNT_WORDS
Coords_2 = 195.0;79.0

Type_3 = AMOUNT_NUMBER
Blocking_Chars_3 = true
Coords_3 = 518.0;67.0

Type_4 = DATE
Coords_4 = 513.0;47.0

Type_5 = NOTES
Coords_5 = 216.0;161.0

# stub

Type_6 = DATE
Coords_6 = 36.0;53.0

Type_7 = PAYEE
Coords_7 = 38.0;78.0;150.0;12.0

Type_8 = AMOUNT_NUMBER
Coords_8 = 50.0;114.0

Type_9 = NOTES
Coords_9 = 28.0;139.0;150.0;12.0

Type_10 = CHECK_NUMBER
Coords_10 = 136.0;37.0

--
Dave Reiser
[email protected]





> On Mar 16, 2018, at 9:29 AM, David Reiser <[email protected]> wrote:
> 
> 
>> On Mar 16, 2018, at 9:10 AM, Jay Ridgley <[email protected]> wrote:
>> 
>> On 03/16/2018 07:43 AM, David Reiser wrote:
>>>> On Mar 16, 2018, at 7:12 AM, Jay Ridgley <[email protected]> wrote:
>>>> 
>>>> 
>>> [snip]
>>>> After looking at the docs you provided, unless I am missing something 
>>>> more, it appears that it is not the check definition that is wrong, at 
>>>> least as far as I can tell. See below..
>>>> 
>>>> I have discovered that if I print the checks 1 at a time and with the 
>>>> position as Top and print, Middle and print and lastly Bottom and print by 
>>>> reloading the same page into my printer ALL THREE checks will be printed 
>>>> in the proper positions.
>>>> 
>>>> In the file /usr/share/gnucash/checks/quicken_wallet.chk there is 
>>>> reference to Check Positions as shown below:
>>>> 
>>>> [Check Positions]
>>>> Height = 204.0
>>>> Names = Top;Middle;Bottom
>>>> 
>>>> However, there is not a definition for either of the 3 listed Names, "Top, 
>>>> Middle, Bottom". Where is that information stored and can it be modified?
>>> Top, Middle, and Bottom just tell gnucash whether to start printing 0, 1, 
>>> or 2 x Height from the top of the page.
>>> Coupled with the “checks on the first page” option, you can tell gnucash 
>>> exactly how to handle the first page of a multiple page check printing. If 
>>> you select Middle position and 1 check on the first page, the first check 
>>> is printed alone in the middle position of the first sheet, while all 
>>> remaining pages contain 3 checks per page (since that’s the format you 
>>> picked).
>>> I never intend to run a printed check back through a printer — too much 
>>> chance to screw up and overprint an existing check. I’ve always removed 
>>> printed checks from the last sheet out of the printer from any check 
>>> printing session. So the next print job is always set to Top position, with 
>>> Checks on First Page set to the number of blank checks available on the 
>>> first sheet.
>>> I only print about 3 checks per year these days, but sometimes they all 
>>> happen in the same print job.
>>> --
>>> David Reiser
>>> [email protected]
>> Thanks, David
>> 
>> Can you explain why the 3rd check prints on the remaining bottom STUB but 
>> NOT on the 3rd check?
>> 
>> I entered TOP for the first position and 3 for the number of checks on the 
>> first page.
>> 
>> Cheers,
>> Jay
>> 
> I’m pretty sure that means that something about the check definition is 
> causing gnucash to think that the middle check is encroaching on the bottom 
> check, so when it increments vertical offset for the last check, it 
> essentially creates a phantom 4th check position. Try reducing or increasing 
> the Height parameter slightly and/or mess with the second Translation 
> parameter (see what happens if you set Translation = 0.0;0.0
> 
> I usually have to fine tune the wallet check definition every time I have new 
> checks printed. The cheap check printers, especially, don’t put all three 
> checks in the identical position from the perforations. The check definition 
> ends up being a compromise on field location among the three checks.
> 
> 
> --
> David Reiser
> [email protected]
> 
> 
> 
> 
> 
> _______________________________________________
> gnucash-user mailing list
> [email protected]
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see 
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.

_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to