Reply to thread

Message

Thanx Inker.

That makes sense. I will do some more researches on that.

Bye
Lars

Edit: After just another brief experiment it look much better. I now able to see the embedded pictures in the fascadeview and it is not slower than before. The routine extracts the thumbnails from the pictures so fast that there is no need to have thumbnails in the "thumbs" folder anymore.

No I have to think of a texture management to get rid of textures that not used any more.
The mentioned OnRetrieveCoverArt is called by the fascadeview if a list item is shown for the first time... so that is perfect to implement my routine.
But unfortunately there is no "OnFreeCoverArt" or something like that.
Do you know how I can analyse with items are shown and with not?

I thought about a List<string> that contains the texture names of the loaded textures, but I have to find out which textures are not needed anymore to free them by time...

Bye
Lars

Edit2:

Mmhh. I still haven't found a proper way to know which items are currently visible and which not. that would be the "cleanest" way to keep only textures in the memory that really needed.

A different approach would be to keep all textures that has been loaded via the modified OnRetrieveCoverArt till the folder is changed... But after browsing a folder with many images that wouldn't be a perfect solution.

Any ideas

<blockquote data-quote="lkuech" data-source="post: 169478" data-attributes="member: 46526">Thanx Inker.That makes sense. I will do some more researches on that.ByeLarsEdit: After just another brief experiment it look much better. I now able to see the embedded pictures in the fascadeview and it is not slower than before. The routine extracts the thumbnails from the pictures so fast that there is no need to have thumbnails in the &quot;thumbs&quot; folder anymore. No I have to think of a texture management to get rid of textures that not used any more. The mentioned OnRetrieveCoverArt is called by the fascadeview if a list item is shown for the first time... so that is perfect to implement my routine. But unfortunately there is no &quot;OnFreeCoverArt&quot; or something like that. Do you know how I can analyse with items are shown and with not? I thought about a List&lt;string&gt; that contains the texture names of the loaded textures, but I have to find out which textures are not needed anymore to free them by time...ByeLarsEdit2:Mmhh. I still haven't found a proper way to know which items are currently visible and which not. that would be the &quot;cleanest&quot; way to keep only textures in the memory that really needed.A different approach would be to keep all textures that has been loaded via the modified OnRetrieveCoverArt till the folder is changed... But after browsing a folder with many images that wouldn't be a perfect solution.Any ideas <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" /></blockquote>

[QUOTE="lkuech, post: 169478, member: 46526"] Thanx Inker. That makes sense. I will do some more researches on that. Bye Lars Edit: After just another brief experiment it look much better. I now able to see the embedded pictures in the fascadeview and it is not slower than before. The routine extracts the thumbnails from the pictures so fast that there is no need to have thumbnails in the "thumbs" folder anymore. No I have to think of a texture management to get rid of textures that not used any more. The mentioned OnRetrieveCoverArt is called by the fascadeview if a list item is shown for the first time... so that is perfect to implement my routine. But unfortunately there is no "OnFreeCoverArt" or something like that. Do you know how I can analyse with items are shown and with not? I thought about a List<string> that contains the texture names of the loaded textures, but I have to find out which textures are not needed anymore to free them by time... Bye Lars Edit2: Mmhh. I still haven't found a proper way to know which items are currently visible and which not. that would be the "cleanest" way to keep only textures in the memory that really needed. A different approach would be to keep all textures that has been loaded via the modified OnRetrieveCoverArt till the folder is changed... But after browsing a folder with many images that wouldn't be a perfect solution. Any ideas ;) [/QUOTE]