Thanks very much, Walter. I'm inclined to try your approach, but I have a
couple of questions that,if you could answer them, will help me understand
it better. First, what is the difference between observe...evt.stop() and
stopObserving? And why would a new div catch the clicks, when
document.stopObserving('click'), which I've also tried, did not? How does
Z-index work here? I'm not familiar with "first()" and hope I'm correct
that it makes an element a first descendant?
Again, many thanks; I'll try your approach this evening,
Jane
On Fri, Sep 17, 2010 at 2:43 PM, Walter Lee Davis <wa...@wdstudio.com>wrote:
> Off the top of my head, I would say observe clicks on a temporary element
> placed over the top of the page and cause them to die, rather than trying to
> disable clicks where you are. By the time your clicks bubble from the
> element they were made on up to the outer shell, it's already too late --
> the click has fired on that element, then bubbled up to the shell.
>
> if(!$('cover')){
> var cover = new Element('div',{id:'cover'});
> cover.setStyle('position:fixed;
> width:100%;height:100%;z-index:1000;top:0;left:0');
> $$('body').first().insert({top:cover});
> cover.observe('click',function(evt){evt.stop();});
> }
>
> later, when everything is ready
>
> $('cover').stopObserving().remove();
>
> Something like that.
>
> Walter
>
>
> On Sep 17, 2010, at 2:26 PM, Jane Hunter wrote:
>
> Hello,
>> I'm making an html/javascript copy of a flash slide-show, probably the
>> first of several necessitated by the iPad. Thanks to Prototype, everything
>> works well in every browser -- EXCEPT, if the user clicks one of the
>> navigation buttons or image buttons before the images are finished loading,
>> the display image doesn't position itself correctly. (The images are of
>> varying sizes and I caculate their position on the fly.) I've tried this
>> (shell being my outermost div), which has no effect at all:
>>
>> <
>>
>> script type="text/javascript">
>> document.observe(
>>
>> "dom:loaded", function() {
>> $(
>>
>> 'shell').stopObserving('click');
>> firstimage();
>>
>> });
>>
>> </
>>
>> script>
>> I can disable each of the buttons and inputs, individually, which is
>> really lame, plus would make me re-iterate through them to un-disable them
>> at the end of the load functions. It would be ideal to disable all the
>> buttons at the beginning of the load process and then have an on-complete
>> event that will re-enable them (and will work in all browsers).
>>
>> Is there a way to do that with Prototype? I'd be very grateful for advice
>> and suggestions.
>>
>> Thank you!
>>
>> Jane Hunter
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Prototype & script.aculo.us" group.
>> To post to this group, send email to
>> prototype-scriptacul...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> prototype-scriptaculous+unsubscr...@googlegroups.com<prototype-scriptaculous%2bunsubscr...@googlegroups.com>
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/prototype-scriptaculous?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Prototype & script.aculo.us" group.
> To post to this group, send email to
> prototype-scriptacul...@googlegroups.com.
> To unsubscribe from this group, send email to
> prototype-scriptaculous+unsubscr...@googlegroups.com<prototype-scriptaculous%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/prototype-scriptaculous?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptacul...@googlegroups.com.
To unsubscribe from this group, send email to
prototype-scriptaculous+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en.
