Yakov,

Cookie history is a very good point! But my FF still works normally after 
removing cookies, and my Opera does not have a cookie history because I 
only installed it a couple of days ago.

The same folder issue is cleared as the same file still works at another 
folder.

However, from your screenshot I did suspect something and made two files in 
my Dropbox's public folder for testing, please try and see if one of them 
works.

   1. 
   https://dl.dropbox.com/u/23745840/MTC_TW266_TWTable143_TWted143--01.html
   2. 
   https://dl.dropbox.com/u/23745840/MTC_TW266_TWTable143_TWted143--02.html
   

Vincent

On Saturday, November 3, 2012 6:39:20 AM UTC+8, Yakov wrote:
>
> Well, first if you can reproduce the problem over http, that's already 
> kind of an option. Next, where do you place Ton's TW? In the same folder as 
> your dev TWs? I mean, although that's unlikely, there can be some forgotten 
> cookie-option (may be you renamed something like "enable TWted" and didn't 
> accounted that somewhere in your code, but as your browsers already have 
> those cookies with old names and values, everything works), could it be so?
>
> пятница, 2 ноября 2012 г., 19:38:08 UTC+4 пользователь Vincent Yeh написал:
>>
>> Ton & Yakov,
>>
>> It seems to me that you are facing the same problem, but I am afraid this 
>> is not an easy one for me (maybe easy for someone else) because Ton's MTC 
>> file works normally with my FF16.02 / Win7x64 (and Opera 12.02 / Win7x64 as 
>> well, see attachment). Well, to be precise it works only if saved locally. 
>> It has the same problem if opened over the internet.
>>
>> I have no idea how to debug under such a situation.
>> Any suggestions?
>>
>> Vincent
>>
>> On Friday, November 2, 2012 10:22:24 PM UTC+8, TonG wrote:
>>>
>>> Hi Vincent, 
>>>
>>> I made a MTC as before (Win7 x64, FF16, TW v2.6.6, TWTable v1.4.3, 
>>> TWted v1.4.3), see [1] 
>>> After reloading the backstage button is present, but with a table only 
>>> the 'C' button can be seen. The 'E' button can't be seen so edit is 
>>> not possible. 
>>>
>>> FYI: The latest "combined" version TableEdit v1.3.12 does also work 
>>> with the plugins mentioned in my last post. 
>>>
>>> Cheers, 
>>>
>>> Ton 
>>>
>>> [1] https://dl.dropbox.com/u/2638511/MTC_TW266_TWTable143_TWted143.html 
>>>
>>> On Nov 2, 11:03 am, Yakov <[email protected]> wrote: 
>>> > Ok, I found out what's the problem: it's with CSS -- the C button 
>>> hovers 
>>> > over the E button, so it's practically "invisible", see the screenshot 
>>> of 
>>> > inspection (it stays in the latest versions). 
>>> > 
>>> > Also, TWtable + TWted add unnecessary scroller to every table. This 
>>> may be 
>>> > connected with the following thing (can be seen on the same 
>>> screenshot): 
>>> > the additional thicker border is only at the top, bottom and left, but 
>>> not 
>>> > at the right; though, inspection shows that the wrapper has normal 
>>> width 
>>> > (not wider than the table). 
>>> > 
>>> > Take you time, Vincent! We'll be patient :) 
>>> > 
>>> > пятница, 2 ноября 2012 г., 11:47:06 UTC+4 пользователь Vincent Yeh 
>>> написал: 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > > Yakov & Ton, 
>>> > 
>>> > > Thank you both very much for the feedback and suggestions. Ton your 
>>> test 
>>> > > file helped me quickly identified the cause to the missing backstage 
>>> > > problem: ignorance of shadowed tiddlers in TWtable. It is now fixed 
>>> in the 
>>> > > next release (see below). It seems to fix the "blocking 
>>> saveChanges()" 
>>> > > issue as well (Ton please help verify this), but I am not sure if 
>>> that also 
>>> > > fixed Yakov's problem that TWtable+TWted combo don't work in Win7 
>>> x64. 
>>> > > Yakov please try and tell me the results. 
>>> > 
>>> > > Other things will have to wait, as I must devote my time into other 
>>> things 
>>> > > for a while. 
>>> > 
>>> > > TWtable v1.4.3 
>>> > 
>>> > >    - (min)http://twtable.tiddlyspace.com/#TWtable.min 
>>> > >    - (regular)http://twtable.tiddlyspace.com/#TWtable 
>>> > 
>>> > >    - Bug fix for missing backstage and blocking of saveChanges(). 
>>> > >          - The missing backstage happens for TW files that start 
>>> with the 
>>> > >          default GettingStarted tiddler or any other shadowed 
>>> tiddlers, 
>>> > >          because TWtable does not touch any shadowed tiddlers. It 
>>> doesn't 
>>> > >          even try to find it, which resulted in a null value for a 
>>> > >          shadowed tiddler and then an exception thrown when TWtable 
>>> is 
>>> > >          retrieving its title (to find its containing DOM element). 
>>> If this happened 
>>> > >          when loading the DefaultTiddler then the backstage, which 
>>> comes 
>>> > >          up after that, would have got no chance to load up. 
>>> > >          - I did not notice this because it did not happen to my own 
>>> > >          minimal test file, which does not start with any of the 
>>> shadowed tiddlers. 
>>> > >           *But this should have happened since transclusion 
>>> > >          synchronization was implemented. Why it did not? Or it 
>>> did?* 
>>> > >       - Some more bug fixes for sorting with SortableGridPlugin and 
>>> > >       TableSortingPlugin. 
>>> > >          - These bugs were partly introduced in codes to fix 
>>> rows/columns 
>>> > >          and the code splitting. *Hope there are not much left*... 
>>> > 
>>> > >    - Changed back to normal font size for table caption. 
>>> > 
>>> > > TWted v1.4.3 
>>> > 
>>> > >    - (min)http://twtable.tiddlyspace.com/#TWted.min 
>>> > >    - (regular)http://twtable.tiddlyspace.com/#TWted 
>>> > >       - Set default text-alignment of a table cell to inherit. 
>>> > >       - Removed some dead codes. 
>>> > 
>>> > > TWtcalc v0.7.3 
>>> > 
>>> > >    - (min)http://twtable.tiddlyspace.com/#TWtcalc.min 
>>> > >    - (regular)http://twtable.tiddlyspace.com/#TWtcalc 
>>> > >       - Defined ROWS() and COLS()/COLUMNS() functions, which counts 
>>> the 
>>> > >       number of rows/columns within a range of cells. 
>>> > >       - Bugs fixed for COLUMN()/COL() and COLUMNA()/COLA() 
>>> functions. 
>>> > >          - These bugs were introduced in codes supporting absolute 
>>> > >          references. 
>>> > >       - Bug fixed with ROUND() function. 
>>> > >          - It was returning NaN when the argument results in 0. 
>>> > 
>>> > > Have Fun! 
>>> > > Vincent 
>>> > 
>>> > > On Friday, November 2, 2012 2:02:38 AM UTC+8, TonG wrote: 
>>> > 
>>> > >> Hi Vincent, 
>>> > 
>>> > >> I had not much time to test the new versions, but I am using 
>>> version 
>>> > >> 1.3.10 daily with much pleasure. Editing tables is so easy now; it 
>>> > >> saves me a lot of time. 
>>> > 
>>> > >> First test with the split versions was not a success (Win7 x64, 
>>> FF16): 
>>> > >> I used the Minimal Test Case made for TableEdit v 1.3.9 (TW v2.6.5 
>>> > >> with config.options.chkAutoSave = true; in a systemConfig tagged 
>>> > >> tiddler), added TWTable v1.4.2-1 and TWted v1.4.2, tagged them 
>>> > >> systemConfig and deleted TableEdit v1.3.9. 
>>> > >> At that moment I realized autosave was not working (I cannot recall 
>>> > >> exactly when it stopped), but manual saving was not possible 
>>> either. 
>>> > >> With help of the bookmarklet "Save current storeArea contents to 
>>> > >> clipboard" from TiddlyTools I could restore the TW but now the 
>>> > >> backstage button had disappeared. 
>>> > >> Anyway, I could edit my sample table. 
>>> > >> May be its a coincidence, but both problems (autosave/backstage 
>>> > >> button) appeared in earlier versions of TableEdit (before the 
>>> split). 
>>> > 
>>> > >> So I started from scratch and checked if autosave worked after 
>>> every 
>>> > >> change. 
>>> > >> * empty TW v2.6.6 
>>> > >> * Added systemConfig tagged tiddler with config.options.chkAutoSave 
>>> = 
>>> > >> true; 
>>> > >> * Added TWtable tagged with systemConfig 
>>> > >> Up till then everything was OK, but after reloading the TW the 
>>> > >> backstage button had disappeared (the same in Chrome 17 portable) 
>>> > >> * Added a tiddler with a table. 
>>> > >> Table could be edited. 
>>> > >> See MTC [1] 
>>> > 
>>> > >> I did not do any further tests. 
>>> > 
>>> > >> For your information, the following plugins work together with 
>>> > >> TableEdit v1.3.10: 
>>> > >> DropDownMenuPlugin 2.1 
>>> > >> GotoPlugin 1.9.2 
>>> > >> ImageSizePlugin 1.2.3 
>>> > >> ImportTiddlersPlugin 4.6.2 
>>> > >> InlineJavascriptPlugin 1.9.6 
>>> > >> ListFiltrPlugin        0.9.1 Beta 
>>> > >> NestedSlidersPlugin 2.4.9 
>>> > >> QuickEditPlugin 2.4.4 
>>> > >> QuickNotePlugin 2.1.0 
>>> > >> QuickOpenTagPlugin 3.0.1a 
>>> > >> RenameTagsPlugin 3.0 ($Rev: 5501 $) 
>>> > >> SaveAndReloadMacro 1.0 
>>> > >> SearchOptionsPlugin 3.0.10 
>>> > >> SimpleMessagePlugin 0.1 
>>> > >> TabEditPlugin 0.32 
>>> > >> TableOfContentsPlugin 2.4.3 
>>> > >> TagSearchPlugin 1.2.0 (2010-10-10) 
>>> > >> TagsplorerMacro 1.3.3 
>>> > >> TiddlerTweakerPlugin 2.4.5 
>>> > >> TiddlersBarPluginMP 1.2.5 
>>> > >> TiddlyFileImportr 0.2.7 
>>> > >> ToggleTagPlugin 3.1.0a 
>>> > >> YourSearchPlugin 2.1.6 (2012-04-19) 
>>> > 
>>> > >> Note: there are 2 search plugins installed. I can switch between 
>>> them, 
>>> > >> but mainly use YourSearchPlugin. Both worked together with 
>>> TableEdit. 
>>> > 
>>> > >> Cheers, 
>>> > 
>>> > >> Ton 
>>> > 
>>> > >> [1]
>>> https://dl.dropbox.com/u/2638511/MTC_TW266_TWTable142-1_TWted142.html 
>>> > 
>>> > >> On Nov 1, 6:40 pm, Yakov <[email protected]> wrote: 
>>> > >> > Vincent, 
>>> > 
>>> > >> > > Thanks a lot for the feedback. Currently I do not have time to 
>>> work 
>>> > >> on 
>>> > >> > > these plugins so you will need to wait a while for the next 
>>> upgrade. 
>>> > >> Here 
>>> > >> > > are a few quick replies I can make at this moment. 
>>> > 
>>> > >> > That's ok, for current use TableEditor 1.3.12 seems to be good 
>>> enough. 
>>> > 
>>> > >> > > Both Opera 12.02 and FireFox 16.02 work in my Win7 x64 (running 
>>> in 
>>> > >> > > VirtualBox 4.1.22 r80657 over Ubuntu 12.04) with TWtable+TWted, 
>>> so I 
>>> > >> am 
>>> > >> > > guessing there might be a plugin conflict in your system. Could 
>>> you 
>>> > >> try to 
>>> > >> > > verify this? 
>>> > 
>>> > >> > No, it's definitely not a plugin conflict as for testing I use 
>>> separate 
>>> > >> > "repositories", where only TableEditor (couple of versions) and 
>>> others 
>>> > >> > (TWted, TWted.min etc) are stored, and only one set is active 
>>> (i.e. 
>>> > >> when I 
>>> > >> > test TableEditor, TWted and others have systemConfigDisable, when 
>>> I 
>>> > >> test 
>>> > >> > TWted + TWtable, others get the tag). 
>>> > 
>>> > >> >  And I also noticed that TWtcalc.min is not hiding all its codes, 
>>> which 
>>> > >> is 
>>> > 
>>> > >> > > due to the use of percentage symbol (%) in the recently 
>>> modified 
>>> > >> COUNT() 
>>> > >> > > function. Maybe will switch to another symbol... 
>>> > 
>>> > >> > Well, you can try @@display:none .... @@ wrapper instead of /% 
>>> .... %/, 
>>> > >> I 
>>> > >> > think this will work. 
>>> > 
>>> > >> > > I see. That was my mistake! Guess I should change it to 
>>> > >> TWtable.min... or 
>>> > >> > > just remove it and show a warning message if TWtable (or 
>>> TWtable.min) 
>>> > >> is 
>>> > >> > > not installed (because people can choose to install either 
>>> one)... 
>>> > 
>>> > >> > This depends on the plugin mechnism. The Requires slice is used 
>>> by 
>>> > >> users to 
>>> > >> > see what is required, but also by TW plugin engine which makes 
>>> sure 
>>> > >> that 
>>> > >> > the required plugins are launched *before* the requiring one (I'm 
>>> not 
>>> > >> sure 
>>> > >> > what is done if the required plugin is not found, but this can be 
>>> > >> > investigated by learning the loadPlugins function [1]). If the 
>>> two 
>>> > >> plugins 
>>> > >> > can be launched in an arbitrary order and work anyway, than I'd 
>>> suggest 
>>> > >> to 
>>> > >> > replace "Requires" by some synonym, so that it would serve for 
>>> users, 
>>> > >> but 
>>> > >> > doesn't do anything with the plugin launch order. 
>>> > 
>>> > >> > > However, I have stopped TableEditor so further development will 
>>> go to 
>>> > >> > > TWtable+TWted combo. We shall fix the first issue before other 
>>> > >> things. 
>>> > 
>>> > >> > Sure, very true. 
>>> > 
>>> > >> > I didn't know about sliders so tables in there are not properly 
>>> > >> prepared. 
>>> > 
>>> > >> > > This will be added in the near future. 
>>> > 
>>> > >> > Ok (it's just previously they worked well, if I remember 
>>> correctly). 
>>> > 
>>> > >> > Looking forward. 
>>> > 
>>> > >> > [1]
>>> https://github.com/TiddlyWiki/tiddlywiki/blob/master/js/main.js#L138 
>>> > 
>>> > 
>>> > 
>>> >  the controls button hovers over the edit button.PNG 
>>> > 99KViewDownload 
>>>
>>

-- 
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/-/7RV2QKObMxgJ.
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.

Reply via email to