printpreview and close button

After calling the printpreviewwindow it is impossible (mac) to close the window again in both developer and client. The button just doesn’t work.

wat do you mean with printpreviewWINDOW?

we have print preview mode (but it is shown in the same window)

I just tested that under the mac and the close buttons works fine in my sample solution. So can you give me some more info?

I will see if I can come up with a sample…

The only thing I do is show the form in printpreview mode instead of printing from it directly. Nothing more and nothing less…

IT2BE:
After calling the printpreviewwindow it is impossible (mac) to close the window again in both developer and client. The button just doesn’t work.

I have this same problem, too… I also have a similair problem that when I close a preview form and navigate to another layout in Recordview, the same preview form is showing up again… Also under Windows XP! (I can send you the URL of the solution if you’dd like to see it for yourself)

please show me (or give me the solution that demonstrates this)

I am now encountering this “problem”. I have a button on a form in a tabpanel that when clicked should go to another form in a table with related records and display the related records in a print preview. When I close the print preview window, I want to go back to the original form with the tab panel. What happens is: NOTHING when I clock the Close button on the print preview, not even the history arrows work. When I go into designer mode from the print preview screen I am already at the form with the tabpanel.
Code is as follows:

//viewPreBill[maBillingInterim]
forms.TEPreBill.controller.loadRecords(matter_to_timeexpense_unbilled)
forms.TEPreBill.controller.showPrintPreview()
forms.maBillingInterim0.controller.show()

maBillingInterim0 is the form with the tabpanel.

Unfortunatly this problem is still unsolved in this post…
Are there any solutions for this issue yet?

Today Karel and I found the issue. This is not a bug but an error in the code. So the issue is closed.

Cheers