On 1/17/2001, 6:53:50 PM EST, Alan wrote about "[Dynapi-Help] List.js and List example
bugs":
> I now have a bunch of follow-up questions, though.
> 1. The list widget allows the user to click on a selected item
> and unselect it. At that point, no item is selected. Is there away to
> ensure that one item is always selected? In dynapi I, I seem to recall
> something like list.allowDeselectAll(false) or something like that. I
> don't see it in the list.js file.
This can easily be done if there is a need for it. If anyone one
wants to do it, go ahead. Or if not, I can give it a whirl.
> 2. When I checked out the latest dynapi from cvs, it merged files
> together and place non-javascript compliant comments showing the
> differences between versions. I had to remove these for the scripts to
> work. Is there a way around that "feature"? I used the CVS command:
> cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/dynapi co
> dynapi
I'm not sure why it did that. However, if you just want the source,
you can try:
cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dynapi export -r HEAD dynapi
> 3. It seems you only changed that one typo. How did that effect
> the addChild() problem I was previously experiencing?!
That was probaly fixed by the changes to the dynlayer and event code
that were made recently.
//Robert
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-help
