Many tanks Mario! On Monday, February 10, 2020 at 5:12:04 PM UTC+3:30, PMario wrote: > > On Monday, February 10, 2020 at 1:14:40 PM UTC+1, Mohammad wrote: >> >> Refereeing to recent discussion on The Good and Bad of qualify: >> https://groups.google.com/d/msg/tiddlywiki/51XMzmLGxfQ/PLkfWWthBAAJ >> >> We know many cases in creating User Interfaces (UI) needs some state >> tiddlers. >> >> I got used to call qualify for such cases, but with the recent >> discussion it seems qualify is designed for purposes one like to keep some >> states permanently and irrespective of current tiddler situation. >> > > I know it's not a real solution for your request but anyway: > > I did create a PR at github > <https://github.com/Jermolene/TiddlyWiki5/pull/4454>, that allows the > qualify-macro to use a isUnique parameter. So you can use > <<qualify "my-unique-title" isUnique:"yes">> .. So the macro doesn't add > -123456 string. It returns the input state text. > >
Are these unique permanent state or will be changed from session to another session or different position of host tiddler in the widget tree? > My question is: >> >> Is there any other ways to create unique stateTiddler? I dont mean do >> this manually? >> > > Sure - but we didn't find it - yet ;) > > >> There are situation, one needs permanent state tiddler to keep data. For >> example in Shiraz dynamic table I uses state tiddler to keep footer data or >> row styles. >> These are not temporary data and it is tedious to define unique state >> tiddler for every table! >> > > As I wrote, you need to work with variables like tiddler-names, tab-names, > list-items and so on. ... And yes creating "real" uniqueness is hard, if it > should be predictable. > > >> The current mechanism I use is qualify macro which is not good for all >> scenario. >> > > that's right. > > >> p.s: >> One KISS solution is to use a helper function which calls now macro >> with [UTC]YYYY0MM0DD0hh0mm0ssXXX format to create a unique title for the >> required state tiddler. >> > > ... And you can remember their names, if you have many of them? > My use case is to put some table properties created interactively by user when Shiraz dynamic table is used. Each table uses a state tiddler like $:/keepstate/dtable/xxx/xxxx/??? so, one time is created I do not need to explicitly refer to it! I cannot use variable or fields here, as I do not know how many tables a user created per tiddler. > -mario > Thank you again -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c709c1c1-f38c-475b-ac1d-a1c428a375b9%40googlegroups.com.
