Digital Workshop

Hi,

I use a exit page to check if a variable is changed and not saved. With an if statement the variable is checked and on true the pub is exited. In preview this works fine, at runtime it fails to performe the action.

Any ideas???

Regards,

Ronnie Dackus

Some weird quirk for preview vs. published? There have been others reported.

What type of publication / published product? Flex, full, etc.?
Is the Exit page in its own Chapter? Are you testing on a Pub var (vs. page var)?
As this is basic section, assume you're doing this all in standard triggers and actions?

You mention 'DLL' in subject. Is it relevant?

Hi,

Thanks for your reply.

The exitpage is in a seperat chapter, variable is a pubvariable, the DLL performs a standard messagebox and some script actions, so no standard actions, but "on show page" the testing is executed.

What I want to do is that on exit of the pub, with the standard windows title bar, variables are checked and actions can be set when a user exit the pub, it has to check if the user has saved his data.

No flexx, standard Opus pub

Regards,

Ronnie

Nothing obvious pops out at me. A couple thoughts. Script object might have to be on the Exit page, or a Master Page it uses. Also, maybe it is a timing issue.... sounds like you are doing several things in quick, streamline fashion. You might try inserting some wait(0.1) statement(s). (or maybe insert an intermediate step to gate the events, figure out where control is lost)

Mmm, this isn't the solution.....thanks for your comment.
I checked it with a different exit page but also it does not go to the exit page. The exit page is in a different chapter and the pub has spiltscreen!

If anyone has a clou.....

Ronnie

Ronnie,

Sorry I'm at a loss. Maybe the wise men will return shortly from Chinese New Year festivities.

Puzzling, why it works one way and not the other.

Have you 'told Opus' you really want to exit the publication?

Ronnie -- please put up a sample imp that demonstrates the problem when published.

Paul

Just craked it!

The problem ocures when there is a split-screen ( Mainscreen and 1 panel ) and the dll-action is called from the main screen ( the ddl-action was called from panel 1 ). Just replace the action to trigger "variable changed" on panel 1. Perhaps this is also the problem with the dialog-box from the print action refered on this forum earlyr?

Thanks for the input!!!!!

Regards,

Ronnie