home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
GUIImage and / or Texture handling change in RC3 / RC4?
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="zeflash" data-source="post: 331974" data-attributes="member: 13641"><p>Not the case. On my system, the dispose happens whenever I play - be it VMR9 exclusive, non exclusive or EVR.</p><p></p><p>I've started working on a patch, there is a disposing even sent by the D3DTexture that we can use. when that happens, the cachedTexture.Frame is notified, calls Dispose, notifies whoever needs to be notified that the texture isn't valid anymore.</p><p>And GUITextureManager subscribes to the Disposed event sent by the CachedTexture (something not done right now), to check if a cachedTexture is disposed, and therefore remove it from the cache list.</p><p></p><p>Basically, the whole chain from D3DTexture to GUITextureManager needs to be reworked. I'd rather see GUITextureManager handles its cache only relying on the Disposed events, instead of calling Dispose & cached.remove. That way no matter what disposes of a texture, it's being taken in account.</p></blockquote><p></p>
[QUOTE="zeflash, post: 331974, member: 13641"] Not the case. On my system, the dispose happens whenever I play - be it VMR9 exclusive, non exclusive or EVR. I've started working on a patch, there is a disposing even sent by the D3DTexture that we can use. when that happens, the cachedTexture.Frame is notified, calls Dispose, notifies whoever needs to be notified that the texture isn't valid anymore. And GUITextureManager subscribes to the Disposed event sent by the CachedTexture (something not done right now), to check if a cachedTexture is disposed, and therefore remove it from the cache list. Basically, the whole chain from D3DTexture to GUITextureManager needs to be reworked. I'd rather see GUITextureManager handles its cache only relying on the Disposed events, instead of calling Dispose & cached.remove. That way no matter what disposes of a texture, it's being taken in account. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
GUIImage and / or Texture handling change in RC3 / RC4?
Contact us
RSS
Top
Bottom