<br><font size=2 face="sans-serif">Thanks /H</font>
<br>
<br><font size=2 face="sans-serif">But...</font>
<br><font size=2 face="sans-serif">This may not work on an executable...</font>
<br><font size=2 face="sans-serif">Also, this is a work around, not a solution.</font>
<br>
<br><font size=2 face="sans-serif">Considering that browsing across images works fine (although it's slow if</font>
<br><font size=2 face="sans-serif">the image is around 3MBs - slow compared to ACDC for example),</font>
<br><font size=2 face="sans-serif">if you can change images simply by setting the filename of the image, </font>
<br><font size=2 face="sans-serif">shouldn't removing the image name be enough? It isn't apparently...</font>
<br>
<br><font size=2 face="sans-serif">I thought of replacing the image object already but the stability of the stack is </font>
<br><font size=2 face="sans-serif">still shaky...</font>
<br>
<br><font size=2 face="sans-serif">And considering I havent' yet started working on image operations (rotation, </font>
<br><font size=2 face="sans-serif">cropping, etc...) this is not a solution I can work with. </font>
<br>
<br><font size=2 face="sans-serif">This application will end up in a cd (read-only...) It's ok for the application since</font>
<br><font size=2 face="sans-serif">the image will always be empty at opening, but it doesn't work for day-to-day </font>
<br><font size=2 face="sans-serif">test and crash development. The problem remains the loss of time and work...</font>
<br>
<br><font size=2 face="sans-serif">Thanks for trying, Bonus game, Play again!</font>
<br><font size=2 face="sans-serif">Xavier</font>
<br>
<br><font size=2 face="sans-serif">On 13/08/2003 11:38:41 metacard-admin wrote:<br>
>In response to Xavier's image display and crash problem, Xbury writes:<br>
><br>
>>To me part of the problem seems that the allocation of the image space in the<br>
>>stack is not "solid" - it is not compactable it seems for one, and once an <br>
>image<br>
>>is decompressed, that's it, you're stuck with that size...<br>
>><br>
>>Is this due to either a flaw in code or the emptying of the image?<br>
>>It's a fact that no one seems to know HOW to empty an image (or imagedata)."<br>
><br>
>If this is the case, instead of updating the imagedata try deleting the old <br>
>image and creating a new one on the fly. Should avoid the problem altogether.<br>
><br>
>/H</font><CODE><FONT SIZE=3><BR>
<BR>
Visit us at http://www.clearstream.com<BR>
<BR>
IMPORTANT MESSAGE<BR>
<BR>
Internet communications are not secure and therefore Clearstream International does not accept legal responsibility for the contents of this message.<BR>
<BR>
The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any views expressed in this e-mail are those of the individual sender, except where the sender specifically states them to be the views of Clearstream International or of any of its affiliates or subsidiaries.<BR>
<BR>
END OF DISCLAIMER<BR>
</FONT></CODE>