This Question is Answered

14 "helpful" answers available (3 pts)
3 Replies Last post: Apr 6, 2008 8:01 PM by Duke

Printing a styled applet cause an error

Apr 5, 2008 2:54 AM

Click to view fukuta's profile BlackBelt fukuta 118 posts since
Oct 17, 2007
Hi, all.
I'm using styled controls library and satisfied with its looking and the flexible way to customize.
It's pretty nice and fun.
But I had just one problem.

If I choose the "Print" of right-click menu and print a styled applet then RTE cause an error.
It says "RuntimeException:invalid memory access".
(This may not be the exact message because I saw a Japanese one.)

Probably you can try any styled applet to see the error.
For example:

{curl 6.0 applet}
{applet manifest = "manifest.mcurl"}
{import * from COM.CURL.GUI.STYLED-CONTROLS}
{install-style-sheet {manifest-url "file", "DEFAULT-STYLE-SHEET"}}
{CommandButton}


What can I do for this?
print-graphic procedure also throws an error.
Click to view Duke's profile Curl Duke 179 posts since
Oct 17, 2007
1. Re: Printing a styled applet cause an error Apr 6, 2008 9:46 AM
I don't see this problem with http://www.curl.com/demos/OrderEntry/start.curl using 6.0.2. I was using an English machine though. Do you see the problem printing that applet, and which RTE version are you using? Which OS?

Also, if you have a full stack trace of the error, you could mail that to support@curl.com.
Click to view fukuta's profile BlackBelt fukuta 118 posts since
Oct 17, 2007
2. Re: Printing a styled applet cause an error Apr 6, 2008 7:33 PM
in response to: Duke
Duke, thank you for your quick reply.

I'm using Curl 6.0.1 on Windows XP Pro SP2.
I have sent the stack trace to curl spport.

But I updated to 6.0.2 and tried to print, now no error occurred.
So I think that my problem is almost solved although it's not known exactly why.

Thanks.
Click to view Duke's profile Curl Duke 179 posts since
Oct 17, 2007
3. Re: Printing a styled applet cause an error Apr 6, 2008 8:01 PM
With the stack trace, I was able to identify the bug, which we fixed in our release 6.0.2. It was our bug 28832.

Thank you for the report.

Here is part of the stack trace which you had sent to support@curl.com (now for others to see):

#0 (0x054e92b7)
#1 Font.destroy (0x0579c4bf+23)
#2 GdiPlusFontInstance.dump-drawable-objects (0x0579c494+12)
#3 FontInstance.free-instance (0x029c59cc+12)