Re: [oXygen-user] Scenario causes Oxegen 11 to become unresponsive
Thank you for the details. See the remarks below. Mark Wilson wrote:
(2) Platform: Vista Ultimate (3) It happens every time I run these files in a debug scenario. I have not tried any other files in this scenario, or any other scenarios since in installed Version 11. They ran quite well in Version 10.
(8). This morning, I ran the scenario again and the following happened. a) I clicked the blue "run" arrow. b) Oxygen reported, Transformation started. c) After about a minute, it reported Transformation Completed", but no text appeared in the text box.
On my Vista Business computer the XSLT debugger completes the transformation in about 3 seconds. I don't think this time difference is caused by a large difference in hardware power between our computers if your computer is able to run Vista Ultimate and the same debugging session ends quickly in Oxygen 10.3 that runs on the same computer.
d) After another minute or so, the text box filled to near the bottom. I tried to slide the text box scroll bar down, but nothing happened. e) After about 30 seconds, </fo:root> appeared at the bottom of the text box.
I get the result document in the Text output view of the debugger on a single line containing 307,318 characters. The the result document starts with <fo:root> and ends with </fo:root>. There is no vertical scroll bar in this view because the whole document is on a single line. I get the same result with Saxon-HE, Saxon-PE and Saxon-EE. Maybe we don't use the same files? Can you check that you tested with the same files that you posted to the mailing list? I attach the files received from you. Best regards, Sorin
I just figured it out: you have word wrap enabled in Preferences. When a very long line is displayed wrapped in a Swing text area the Swing UI is unresponsive. It is a known problem in Swing for which we don't have a workaround yet. The bug is that Oxygen should not apply the line wrap preference to the output view of the debugger because the debugger result is most helpful if preserved as is. We will fix that in the next version. As workaround please disable the option line wrap in Preferences -> Editor -> Pages -> Text when you generate very long lines in the debugger. Regards, Sorin Sorin Ristache wrote:
d) After another minute or so, the text box filled to near the bottom. I tried to slide the text box scroll bar down, but nothing happened. e) After about 30 seconds, </fo:root> appeared at the bottom of the text box.
I get the result document in the Text output view of the debugger on a single line containing 307,318 characters. The the result document starts with <fo:root> and ends with </fo:root>. There is no vertical scroll bar in this view because the whole document is on a single line. I get the same result with Saxon-HE, Saxon-PE and Saxon-EE. Maybe we don't use the same files? Can you check that you tested with the same files that you posted to the mailing list? I attach the files received from you.
Best regards, Sorin
participants (1)
-
Sorin Ristache