libsvg-android

Problem with svgAndroidDestroy

Asked by monopula

Hi, there

I have a little problem.
When I use the following:

long id = svgAndroidCreate();
svgAndroidParseBuffer(id, svg);
svgAndroidDestroy(id);

All works fine.
But in this case:

long id = svgAndroidCreate();
svgAndroidParseBuffer(id, svg);
svgAndroidRender(id, canvas);
svgAndroidDestroy(id);

I've got the error:
Too many PopLocalFrame after destroy.

Thanks.

Question information

Language:
English Edit question
Status:
Solved
For:
libsvg-android Edit question
Assignee:
No assignee Edit question
Solved by:
monopula
Solved:
Last query:
Last reply:
Revision history for this message
pltxtra (pltxtra) said : 		#1

Hi,

do you manage to build and run the example application?

Can you send me the SVG-file you are trying to render?

   Regards
     Anton

Revision history for this message
monopula (monopula) said : 		#2

Hi,

The project I tried is http://www.codeproject.com/KB/android/AndroidImageViewSVG.aspx
It compiles and runs ok.
The image is the same.

Thanks

Revision history for this message
pltxtra (pltxtra) said : 		#3

OK, but it works then? It is just that you get warnings about too many pops?

That is a known problem, but it will not cause any serious effects on your application.

Revision history for this message
monopula (monopula) said : 		#4

I clear exceptions in _svg_android_state_destroy. Now it works ok.
Thanks.

Revision history for this message
pltxtra (pltxtra) said : 		#5

Hi, you shouldn't have to clear exceptions though... Can you send me the
image you used, or a direct link to it? I will try it with my own example.

On Sun, Nov 6, 2011 at 12:50 PM, monopula <
<email address hidden>> wrote:

> Question #176473 on libsvg-android changed:
> https://answers.launchpad.net/libsvg-android/+question/176473
>
> Status: Needs information => Solved
>
> monopula confirmed that the question is solved:
> I clear exceptions in _svg_android_state_destroy. Now it works ok.
> Thanks.
>
> --
> You received this question notification because you are a direct
> subscriber of the question.
>