Bug #76464 Rearrange EERDiagram in Print Preview Causes Error
Submitted: 23 Mar 2015 18:38 Modified: 23 Apr 2015 22:33
Reporter: David Tuttle Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.2.4.12437 build 2426 OS:Windows (Windows 7 x64)
Assigned to: CPU Architecture:Any
Tags: EER Diagram, print preview, Visual Styles, workbench

[23 Mar 2015 18:38] David Tuttle 
Description:
Error Message: "Visual Styles-related operation resulted in an error because visual styles are currently disabled in the client area."

I wanted to print an EER Diagram. My Printer does not support Tabloid size, and the Page set up opened in tabloid size. I changed to paper size to US Legal, because the printer does support that.  I switched to Print Preview and tried to rearrange the tables in the diagram to make them better fit the paper size.  This caused the error message above.

How to repeat:
I opened an existing model file and saved it with a new name.  I renamed the schema and renamed the references.  I saved the model.

I opened the existing EER Diagram, went to Page Set-up and changed the paper size from Tabloid to Legal.  Went to Print Preview and discovered that the diagram was not fitting properly on the legal sized page.  I started to re-arrange the diagram (while still in print preview) and got the above error.

Suggested fix:
This error (visual styles are currently disabled in the client area) implies that I could (or should have) do something to enable Visual Styles.  Perhaps this condition should fail gracefully and instruct me to enable or install something.

Note that searching for "visual styles" in the 5.7 Reference Manual got me nothing.
[23 Mar 2015 22:33] MySQL Verification Team 
Thank you for the bug report. Please try version 6.2.5 (WorkBench didn't allowed me to re-arrange the diagram while in print preview, for that I needed to close the print preview screen). Thanks.
[24 Apr 2015 1:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".