Release of v3.0.3 Some bug fixes for compatibility issue with NestedSliderPlugin (and hopefully fixed the backstage issue as well), and a few of others. See release note at TiddlySpot <http://twve.tiddlyspot.com/#[[Release%20Note%20v3.0.3]]> or TiddlySpace <http://twve.tiddlyspace.com/#[[Release%20Note%20v3.0.3]]>.
Happy Dragon Boat Festival! Vincent On Wednesday, May 28, 2014 12:09:45 AM UTC+8, Vincent Yeh wrote: > > Hi Yakov, > > On Tuesday, May 27, 2014 9:27:24 PM UTC+8, Yakov wrote: > > Hi Vincent, > > > > > > 2. Lists > > > 2.2 Changing of the list order is rather slow > > > Hmmm, I just noticed in my example > <http://twve.tiddlyspot.com/#%5B%5Btwve--Example--List%20Items%5D%5D> > that *it caused an infinite loop when I tried to move down the last item*, > but worked quite smoothly in other cases, even when moving up the very > first one (well, you may get strange results but that's how TiddlyWiki > renders lists, not the *twve*). Are you saying it is slow in general, or > just cases similar to what I mentioned? If it is general then I would guess > it's some interference with other plugins. > > > Well, no, for me (in FF/Opera) in a list as simple as > * one > * two > * three > moving the first or the second item down takes 3-4 seconds (even if that's > the only open tiddler). > > > I am guessing that could be the AutoSave feature (I remember you had once > mentioned about this?). > > In v3.0.2 (and earlier versions) moving an element (such as a list item) > includes setting the tiddler text twice, which would trigger the saving > action twice if AutoSave is enabled. That could be time consuming. I can > reduce the time of setting tiddler text to once, should save half of the > time but I don't know how to save more with AutoSave enabled. Usually I > disable the AutoSave option and moving elements is very smooth. > > Yes, very probably it's autosaving. And moving table rows has sort of the > same speed as colomn moving. How about an option that will control whether > autosaving should be called? > > > Yes, you are right! I already forgot there is one such option since the > very beginning! Check the option chktwveCoreManualSave and the > autoSaveChanges() function will not be triggered every time but only when > you press the SaveChanges command explicitly. > > > > > > > > > 3.2 Inline editing (at least adding/removing colomns) seem to remove > additional classes. Say, I have a borderless table > |borderless|k > |text| > After I add a new colomn, the table becomes with borders (it is ok for > edit mode, but in view mode I would like to have my CSS applied). The > |borderless|k part is not removed, if the tiddler is reopened, the > borders are gone again. > CSS here is > .borderless, .borderless tr, .borderless th, .borderless td { border: none > !important; } > Note the !important part: without it, the stying is not applied at all -- > I would consider this as a bug, too. > > > This I really have no idea. The *twve* does not do anything about styles > because I have very limited knowledge about CSS statements. If that is a > bug in *twve*, that must be due to the nothing be done about styles. In > that case it may take a long time to fix... > > > Ouch. I wanted to check if the DOM classes are removed, but the bug is no > longer reproducible.. Let's forget about it until I can reproduce it again. > > However, the need to add the !important part to CSS stays. > </blockquot > > ... -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
