ImageView Queue should cancel loading when it is no longer required
Reported by Charles Jolley | May 27th, 2008 @ 12:13 AM | in REL 0.9.21
Currently if you set the source of an image view it goes into a loading queue. However, if the image
view subsequently changes this src URL, the item in the queue will still load, causing the the image
to "flash" to this old image before the new one loads.
Instead, the image view should be able to cancel loading of its image if it's src is changed before it
is loaded. This would allow the image queue loading to be faster as well since only actually required
image will be loaded.
Comments and changes to this ticket
-
Charles Jolley June 28th, 2008 @ 02:07 PM
- → Tag changed from “” to “feature”
- → State changed from “new” to “open”
-
Erich Ocean (onitunes) September 30th, 2008 @ 04:30 AM
- → Milestone changed from “Unscheduled” to “REL 0.9.21”
- → Assigned user changed from “” to “Erich Ocean (onitunes)”
-
Erich Ocean (onitunes) September 30th, 2008 @ 04:30 AM
- → Title changed from “ ImageView Queue should cancel loading when it is no longer required” to “ImageView Queue should cancel loading when it is no longer required”
-
Erich Ocean (onitunes) November 8th, 2008 @ 09:25 AM
- → Assigned user cleared.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
SproutCore: JavaScript Application Framework
Source available from github
The Git repository resides at http://github.com/sproutit
Check out the current development trunk with:
git clone git://github.com/sproutit/sproutcore.git
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Submitting Patches
Resist adding new tags, use the ones in the tag cloud already. If you are submitting a patch or a pull request from a fork, tag the ticket as a "patch". If you are submitting a new feature enhancement, tag it as "enhancement". If you are submitting a fix for a bug, tag it as "fix".
Thanks!
We're glad you're contributing. Feel free to drop by the Google Group as well to let us know you are involved.
