Digital Workshop

I'm using Opus Pro 5.5, and 6.0; the problem occurs in both versions.

Problem:

I've created a Print Action using a script. The script is located in a Style page.

When I test it in Preview mode, it works fine. The Printer Dialog box is displayed, and I can use the mouse to continue the action, or cancel the print action.

When I Publish the same publication, and test the same print action, the Printer Dialog box appears, however, the mouse is blocked from passing over the Printer Dialog box. The only way to print, and close the Dialog box is by using the keyboard.

If I use the internal Print Action, it works fine in Preview mode, and in when published, so obviously there is a short-coming in the scripting capabilities.

This is somewhat disturbing because I've assumed that the Published
version should operate the same as the Preview; that is obviously not true in every case.

Am I missing something ? Is there some way to resolve this issue ?

I was hoping the V6 would resolve it, but that didn't happen.

I'm open to any suggestions.....

Steve Hawley

Can you attach an imp to demonstrate the problem?? or the script you are using.

Sandy

Hi Sandy,

The attached file is an example of the printer problem that I'm having..

Thanks,
Steve

Can you post the actual IMP. I can't try anything with the EXE. I noticed that a double hand appears as soon as I mouse over the text...it that a custom cursor or part of the problem?.


If I have the IMP, I can have a play with it. If you prefer...mail it to me.

Rgds

Sandy

Woops.....

Sorry, I thought I sent the IMP.... this attachment is the IMP, only.

The double-cursor is a relic of creating the the sample IMP. I removed
it, and the Print Action still fails.

Thanks,
Steve

No good news so far I'm afraid.
At first I thought it was something to do with the way you were passing the parameter to the PrintPage script, but then I created a new and very basic pub with two pages.... button on the first page to print the second page.

PrintPage("Page_2",true,true)
with exactly the same result. Works in preview, not when published.
However PrintObject seems to work fine. Can you use this as an workaround in some way???

I tried
PrintPage(ThePage,false,true) and this seems to work fine---do you really need the cancel dialogue??

Sandy

Hmmmm.... I poste a reply yesterday, but I don't see it..

Anyway, the Printer Dialog box is necessary to allow the user to
select the printer, or cancel. The cancel-while-printing is not necessary.

I was hoping that there was some error in my coding, but since it appears to be okay, I'll have to replace the scripted print function, with the
internal Print Action. I'll have to do this to several other publications.
It's a pain.

Since the scripted print works fine in Preview mode, but not when the publication is published, it's obvious that there is a bug in Pro 5, and 6.

I hope DW can fix this; it doesn't seem like a terribly difficult chore, since it fails consistently, and obviously. I was hoping the problem would be resolved in V6, but that didn't happen.

Anyway, thanks for your help !

Steve

Steve,

It's got to be the 'greens'. Save the trees, the water-beetles, etc. Less printing saves lives.

Try this.
Insert a regular (non-Master page) in somewhere before your current page. For test purposes, just put some 'liberal' text sample on it.

Then publish and test your print.

( I think it's the 'minus 1' on Button 3146 script. )


I did a test... Web type pub which did print to PDF output successfully.

good hunting,
Lar

Hi Lar,

I tried what you suggested, and it still fails; in the exe version, I'm not able to move the mouse over the Printer Dialog box.

I also tried removing the "-1" logic, and replaced the exisitng script with
the literal name of the page, i.e., PrintPage("Page_021_",true), and it
still fails.

The page prints fine, it's just that I can't choose the printer, and/or cancel the print job using the Printer dialog box.

Again, it does work fine in Preview mode, but not in the published mode.

I did notice that in the exe version, when I click the Red button the
Printer Dialog box is displayed, and then if I print the Green button (which uses the internal Print Action), the exe goes into limbo and is inop. So, obviously there is a conflict between the internal Print Action, and the scripted PrintPage() function.

Thanks for your help !

Steve

P.S.

Astobeing'green',I'vefoundthatIcanconservepaperifIremoveallofthespacesbetweenthelettersonthepage.

By way of update.



I just tried the attachment above, published it without change, and it works fine. The 'Red Button' with Opus Script prints as intended.

This is Feb '09. I am using OpusPro v6.4 on Vista Home Premium. (BTW, not sure if it makes any difference, but I had downloaded and manually installed the 'new' Opus Plexus Plugin in January.)

The DW crew are 'world fixers' evidently.

[Lar Edit 0207] Maybe not as simple as I thought. There is another post discussing 'external print' issues. On my system/configuration, I do have MS Office 2003 (w/Access DB) installed. So maybe the 'ability to print' is tethered to MS Office as discussed...
viewtopic.php?t=651&postdays=0&postorder=asc&highlight=print+html2&start=45