This is a very interesting topic. depends on who you ask. Here, i believe
it emphatically "yes", but this is not a bug - it's a consequence of
design decisions.
however in your case - it's thankfully a much easier fix. Browser caching
can cause this! try using the getTime() method to make a throwaway query
string argument so that your url looks like
http://something.com/picture.jpg?throwaway=789324934
so that the throwaway argument changes every request and you will be able
to reload your image. Am i close?
james
On Thu, 11 Mar 2010 01:37:43 -0500, <[email protected]> wrote:
Is it considered correct behavior, when an attribute is 'updated' with
same
value, that the "on changed" event is not generated?
Specifically, in my case I am 'updating' a view's resource with URL of
same
value, but which has an updated image data, and thus I need the updated
image to
load. But OL does not generate the "onresource" event in this case.
I wonder, should the "on changed" event mechanism fire anytime the
attribute is
touched, regardless of the old/new value?
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
