wolfgang, Thanks for the fruitful feedback. Since I never had a large table so I never tested those cases. I will start to see how it works with large tables. However, since I have no idea how to do those "fixed rows/columns" things, I would need some time to build an example. If you could provide me one to test on that would be wonderful. Thanks again for the useful comments! :-)
Vincent On Saturday, August 18, 2012 10:44:56 PM UTC+8, wolfgang wrote: > > Thanks a lot for continually working on improvements. :-) > > However, usually my sheets are bigger than any screen, and therefore, does >> anyone know if 1-2 rows at the top, or to the left could fixated in their >> position so that they don't scroll out of view? Maybe just some CSS to >> accomplish this? >> >> Tried to create a larger text based table (an interactions matrix for > nutrients) and experienced quite some momentary bugs: like deleting the > table by adding rows or columns and leaving a 'undefined' as only content, > Or renaming B vitamins (B1, B2,..) in the table header and first column to > 'C's. And worse, leaving a 0 byte TW without anything after a saveChanges > (though that has happened before with the latest TW version and I therefore > had 'save backups' enabled :-). Since I can't consistently reproduce these > serious errors, and they also seem to get much less - it would be difficult > to find out if some other plugins interacted or other reasons at the moment. > > Tried to create a position fixed first row and column by transclution - > but that isn't a solution unless all cell widths are made equal. Also > having the fixed header row and first column transcluded brought up the bug > that TableEditor seemingly arbitrarily chooses on which of the 3 tables it > adds the editable class (in a 'editable' globally enabled TW) irrespective > of their order in the tiddler or <noedit> added to all it's cells (it > prefered the first row column table). An other difficulty with the > automatically adjusted cell widths and entering 1 or 2 sentences in table > cell is, that the edit field most often isn't wide enough, additionally the > height isn't larger than it's width. Which often gives an edit field about > 3 lines of only 3 letters wide! And makes TableEditor practically useless > for entering text at this point. > > Guess the easiest solution with largely variable cell widths (and heights) > in view mode could be the existing feature of GridPlugin to initially show > only a certain number of characters in each cell - it's full content only > with a click into the cell. For edit mode there would have to be a minimum > width for the cell being edited (at least 8 characters per line). > > Enough for now :-) > >> >> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/3PUtNOxFgPsJ. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
