The code I'm seeing on your site says version 0.2. The current code should say 0.21. Maybe you didn't upload after experimenting?
Just checking. Thanks, Mark On May 20, 12:47 pm, Morris Gray <[email protected]> wrote: > Hi Mark, > > I've been unsuccessful in making antisesame work on my site. I've > disabled your other versions, tried it on various little branches, I > copied and pasted your antisesame code (but not your tiddlers I admit) > I am a bit thick in the head right now though. > > Perhaps you could try it on the latest version of my site since that's > what I tried it on. You got it all fresh in your mind so you might > find I was doing something wrong. > > Oh I did notice the +s and -s do get mixed up when trees are open on > startup, I think that was always the case. > > Morris > > On May 21, 4:24 am, "Mark S." <[email protected]> wrote: > > > Hi Morris, > > > I've just updated plugin2 with a new, undocumented feature. > > Undocumented, because we'll have to see if its worth it. > > > Now when you specify the settings, you can specify a "sesame" and an > > "antisesame" tag. Like > > > 'collapsed: false, antisesame: "closed" ' > > > "sesame" (case matters) gives the name of the tag to indicate that a > > tiddler should be OPEN by default. "antisesame" gives the name of the > > tag to indicate that a tiddler should be CLOSED by default. > > > So far, I haven't found any use for "sesame" -- in fact, I'm not > > entirely sure that it works -- it may be that it only works when you > > have a rootless tree. > > > But for your purposes, the 'antisesame' does seem to work. So if you > > say that you want a menu to be open (collapsed: false), but specify > > 'antisesame' as "closed", and then tag each of the tier two menu items > > with "closed", then the tree will be open, but each of the branches > > will be closed. > > > I allow you to specify your own tags, in case you're already using > > "open" and "closed" for something, or in case you want to have > > different menu trees with different defaults. > > > The extra code to do this may slow things down a bit ... not sure. > > Seems fine on FF so far. Oh, code seems to work on IE 6 so far as > > well ... if you want to put that on your front page. > > > Persistence problems ... well, one thing at a time ;-) > > > Thanks, > > Mark > > > On May 20, 2:51 am, Morris Gray <[email protected]> wrote: > > > > On May 20, 1:53 pm, "Mark S." <[email protected]> wrote: > > > > Well done Mark. I have added Plugin2 to my site. It is working just > > > fine, have a look. > > > > For a big menu like I'm using to see how it feels; opening the whole > > > thing is a bit over the top. > > > > However I put it in the persist state and it remembers where it was > > > when you last had it open during any session but doesn't persist with > > > a reload. > > > > The next problem is how to keep it partially open because I'd like a > > > chosen number of top levels to be open on startup. You might be > > > interested to know that my first three levels are three different > > > tiddlers and are where they are because of tags. However they > > > obviously inherit the open all command. > > > > > I hope you don't mind, but I've borrowed your stylesheet setup. > > > > Not at all but we do need to work something out for the images > > > though. I can't guarantee I can keep them on my site for everyone for > > > all time. You might try ImageShack. > > > > Keep on truckin' :-) > > > > Morris > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
