Re: Re[2]: [Dynapi-Help] dynapi ...

[Richard :o]

Hi, Two more things I found: Would you consider applying the following changes to pathanim.js,   PathAnimation.prototype.stopAnimation = function (notinvoke) { if (this.pathPlaying && this.pathPlaying.resets && !this.cancelThread && this.dlyr!=null) this.dlyr.moveTo(this.pathPlaying[0],this.pathPlaying[1]); this.stop(); if (this.dlyr != null){ delete this.pathPlaying; // only deletes unstored path //moved up 2 rows this.playing = false; //moved up 2 rows if(!notinvoke){ // if this.stopAnimation(true)== no onpathstop if (this.dlyr != null)this.dlyr.invokeEvent("pathstop"); }; }; }; The two rows have been moved up, so when pathstop is invoked, the animation can call itself again from its own eventlistener, without this.playing still being true. the notinvoke parameter was introduced so path.stopAnimation() will invoke the onpathstop eventlistener, firing the next sequence, while: path.stopAnimation(true) won't invoke anything, so the animation stops completely. The second point is text selecting during scrollbar-drag. In "dynapi.gui.scrollbar.html" this is very obvious if your mouse leaves the large scroll square. If you put Michael Burges' code:     if (is.ie) document.body.onselectstart = function() { return false } directly in your document, there is no text selecting, but I haven't found a way to incorporate it in the widget, and have text selectable again after the scroll with this line:     if (is.ie) document.body.onselectstart = null the selecting/not_selecting part works fine, but I can't get any eventlistener in scroll.js to activate/de-activate them correctly each time.   Keep up the good work, the snapshot looks good.   Cheers, Richard  :o   [EMAIL PROTECTED] www.richardinfo.com (Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2)     ----- Original Message ----- From: "Robert Rainwater" <[EMAIL PROTECTED]> To: "DynAPI Help List" <[EMAIL PROTECTED]> Sent: Wednesday, January 17, 2001 9:46 PM Subject: Re[2]: [Dynapi-Help] dynapi ... > > I want to release it soon.  However, there are a few things to be done > first: > > 1 - Fix some loadpanel bugs (one I have already fixed) - the loadQueue > seems to be the major problem > > 2 - Fix the list widget so that it will be fast enough to be usable > > 3 - Finish up the documentation (this may possibly not be in the next > release) > > 4 - Make sure the event code is stable (with the latest of IlMaestro's > updates, its seems to be) > > When these are done, then I think we can release the next version. > However, the latest snapshot seems to be pretty stable, so you > shouldn't hesitate to start using its new precreate widget structure. > Especially since the layer creation in NS is much more stable than the > previous release. > > -- > // Robert Rainwater > > On 1/17/2001, 3:31:01 PM EST, Jason wrote about "[Dynapi-Help] dynapi ...": > > > Is there any timeline for the next planned stable release?  I'd like to be > > able to support cross-browser (4.0-6.0+) DHTML widgets in Fortune 500 web > > apps.  I need a stable API in order to do this. > > > Thanks, > > Jason > > > ----- Original Message ----- > > From: "Dan Steinman" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Tuesday, December 19, 2000 11:14 PM > > Subject: Re: [Dynapi-Help] dynapi ... > > > >> First thing you should do is get the latest copy of the source using CVS. > > There is instructions here: > >> > >> http://sourceforge.net/cvs/?group_id=5757 > >> > >> The cvs software for RedHat is included on the Redhat CD, or can be > > downloaded from ftp.redhat.com > >> > >> The 11/07 dynapi release is a bit out of date now, some significant > > updates have been made since then and should release most of the problems. > > I develop under Linux (in fact RH 6.2 also), and everything works very well > > on Netscape now. > >> > >> Dan > >> > >> On Tue, Dec 19, 2000 at 05:15:48PM -0500, Daniel Shriver wrote: > >> > Hi, > >> >      My system is Linux Zoot (6.2), with Netscape 4.72 running on it, I > >> > have the 11/07/2000 build of the dynapi. > >> >      I'm working through the tutorial on the dynapi 2 and I'm finding > >> > erratic behavior.  For one thing I find that examples on dragging work > >> > one day and not the next (giving an error in the dynapi.js of: > >> > > >> >                 JavaScript Error: > >> > file:/home/DShriver/DHTML_INFO/dyn2_11_07_2000/dynapi/js/dynapi.js, > >> >                         line 92: > >> > > >> >                 group is not defined. > >> > > >> >                 JavaScript Error: > >> > file:/home/DShriver/DHTML_INFO/dyn2_11_07_2000/dynapi/js/dynapi.js, > >> >                         line 45: > >> > > >> >                 DynDocument is not defined. > >> >             ) > >> > > >> > The code looks reasonable and it looks like the variables should be > >> > defined (there are statements setting them up, so I could only see them > >> > being undefined if their building blocks were null) and I have not > >> > touched the API. > >> > > >> > Also the previous day I got as far as the widget tutorial and found that > >> > when I tried open the widget page in my browser > >> > it killed the browser (I repeated this behavior many times, even after a > >> > fresh rebooting). > >> > > >> > Is there some strange issue with the API not working quite right on > >> > Linux or with 4.72, or both? Or did I set things up incorrectly. > >> > > >> > Also is there some good DHTML ref for building "widgets" out there.  All > >> > I want (right now) out of DHTML is scrollable > >> > windows.  I've done a LOT of surfing to find them and have found > >> > numerous toolkits but they all seem to have one or more of the following > >> > flaws: > >> >             -big gaps in browser cross compatability > >> >             -buggy (some of them just don't work right, some have > >> > problems that can be fixed by me refreshing the page but > >> >                             I view this as unacceptable to the end user, > >> > ...). > >> > I probably will not want anything else for quite some time and when I do > >> > it will most likely be some other vanilla content navigation tool.  The > >> > big goal for me is solid browser cross compatablity.  It would be > >> > acceptable for the tools to only work with  IE4 (and beyond), and  NS4 > >> > (and beyond) on various OS's and boxes. > >> > > >> > Ideally I'd like to work with some toolkit that does all the "magic" for > >> > me (branching around different DOM's and browser flaws) leaving me to > >> > deal with only logic and presentation issues. > >> > > >> > > >> > > >> > _______________________________________________ > >> > Dynapi-Help mailing list > >> > [EMAIL PROTECTED] > >> > http://lists.sourceforge.net/mailman/listinfo/dynapi-help > >> > >> _______________________________________________ > >> Dynapi-Help mailing list > >> [EMAIL PROTECTED] > >> http://lists.sourceforge.net/mailman/listinfo/dynapi-help > > > > _______________________________________________ > > Dynapi-Help mailing list > > [EMAIL PROTECTED] > > http://lists.sourceforge.net/lists/listinfo/dynapi-help > > > > _______________________________________________ > Dynapi-Help mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/dynapi-help > ____________________________________________________________ > Get your free domain name and domain-based e-mail from      > Namezero.com. New!  Namezero Plus domains now available.    > Find out more at: http://www.namezero.com                   >