[tw] Re: [tw5]list filter field !value question

[Matabele]

Hi Mans

I am open to suggestions. I have debated whether to retain the set and 
setTo attributes of the <$maketid> widget myself (they are a legacy from 
the <$linkcatcher> widget which was my template for developing both the 
<$seffield> and <$maketid> widgets.)

The set and setTo attributes of the <$button> widget can take care of state 
variables (this must be the primary reason for their existence.) The set 
and setTo attributes of the <$maketid> widget appear somewhat redundant 
(and clearly create confusion.)

Should they be retained? Can anyone think of a use for them (remembering 
that they target 'currentTiddler' by default), or should they be removed?

regards

On Saturday, May 31, 2014 5:50:37 PM UTC+2, Måns wrote:
>
> Hi Matabele
>
> Thank you for explaining things :-)
>
> Sorry if I'm still confusing things however:
>
> I'm not sure if I would prefer that:
>
> >the set and setTo attributes of the <$maketid> widget could be removed 
> entirely (after all, a <$setfield> widget is easily added.) 
>
> You can't have more than one set of set and setTo attribute in one 
> <$maketid> call - or can you?
> Isn't that why you introduced the <$setfield> widget in the first place? - 
> or is it because <$setfield> is more "generic" ? (eg. can be added to the 
> button macro)...
>
> I hope you will excuse my obvious confusion in these matters - however I 
> haven't tried to create widgets or plugins myself - for a reason  
>
> Cheers Måns Mårtensson
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Måns]

Hi Matabele

Thank you for explaining things :-)

Sorry if I'm still confusing things however:

I'm not sure if I would prefer that:

>the set and setTo attributes of the <$maketid> widget could be removed 
entirely (after all, a <$setfield> widget is easily added.) 

You can't have more than one set of set and setTo attribute in one 
<$maketid> call - or can you?
Isn't that why you introduced the <$setfield> widget in the first place? - 
or is it because <$setfield> is more "generic" ? (eg. can be added to the 
button macro)...

I hope you will excuse my obvious confusion in these matters - however I 
haven't tried to create widgets or plugins myself - for a reason  

Cheers Måns Mårtensson

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Matabele]

Hi Mans

On Saturday, May 31, 2014 2:27:24 PM UTC+2, Måns wrote:
>
>
> As I understand it the maketid widget creates the tiddler if it doesn't 
> exist already - and appends the specified field and fieldvalue at the same 
> time..
>

No -- the new tiddler gets created from the template with the title and 
tags specified (these two fields write over the 'title' and 'tags' fields 
of the template before it is created.) The setting of the value of the 
text-reference is done separately and may be subject to the vagaries of 
timing (presently the new tiddler appears to be created before the value of 
the text-reference is set.) This can be seen since the target of the set 
and setTo attributes may differ from the newly created tiddler.


> If the tiddler doesn't exist already the maketid widget and set field 
> widget will write fields & values to the existing tiddler, however the 
> maketid will also create a new tiddler with a numbered appendix to the 
> title - and this tiddler won't get fields & values set by the widgets...
>

Again, not quite correct. The message parameter generated by the <$maketid> 
widget will be the same as the title of the new tiddler (even if a new name 
is generated in the case that the title specified already exists) -- all of 
the <$setfield> widgets will, therefore, target the newly created tiddler.

The set and setTo attributes of the <$button> and <$maketid> widgets, 
however differ -- they target 'currentTiddler'. In the case that the target 
specified for these attributes is the same as the new title, all will be 
well provided that there is no existing tiddler with that title. If there 
is, the <$maketid> widget will change the title and create a new tiddler 
with a different name without changing 'currentTiddler'.

I can not change the behaviour of the <$button> widget, and by choice I 
chose to mirror this behaviour in the <$maketid> widget. This could be 
changed -- or the set and setTo attributes of the <$maketid> widget could 
be removed entirely (after all, a <$setfield> widget is easily added.) 

In any case -- the best practice is to use only <$setfield> widgets if you 
intend to target the new tiddler -- use the set and setTo attributes of the 
<$button> and <$maketid> widgets for other purposes.

regards

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Måns]

Hi Matabele

Neat :-)

As I understand it the maketid widget creates the tiddler if it doesn't 
exist already - and appends the specified field and fieldvalue at the same 
time..

If the tiddler doesn't exist already the maketid widget and set field 
widget will write fields & values to the existing tiddler, however the 
maketid will also create a new tiddler with a numbered appendix to the 
title - and this tiddler won't get fields & values set by the widgets...

It seems a little unuseful that maketid will create an extra tiddler 
without fields & values
What might an use case be?

Hmm. Maybe it would be good if maketid didn't create a new tiddler - if the 
targetted already exists - however this might be the basis for writing yet 
another widget - or have some additional parameter telling maketid not to 
create a tiddler if the original tiddler title already exists...  

As if I knew what I was talking about ... ;-)

Cheers Måns Mårtensson


Den lørdag den 31. maj 2014 12.51.24 UTC+2 skrev Matabele:
>
> Hi Mans
>
> I had an additional thought - the following code might appear to 
> synchronise the target:
>
> <$tiddler tiddler="Target One">
> <$setfield set="!!field3" setTo="this is the text from the setfield 
> widget">
> <$maketid title={{!!title}} set="!!field2" setTo="this is text from the 
> maketid widget" message="tw-set-field">
> <$button set="!!field1" setTo="this is the text from the button widget" 
> message="tw-new-tiddler">Test
> 
>
> However this will be so only in the absence of an existing tiddler titled 
> 'Target One'. If 'Target One' exists, the maketid widget will create 
> 'Target One 1' which will be targeted by the setfield widget (field3) -- 
> however the set and setTo attributes of the button and maketid widgets will 
> target the existing 'Tiddler One' (field1 and field2.) 
>
> regards
>
> On Saturday, May 31, 2014 10:26:16 AM UTC+2, Måns wrote:
>>
>> Hi Matabele
>>  
>>
>>> Exercise caution when using the 'set=' and 'setTo=' attributes of the 
>>> <$button> and <$maketid> widgets in the same way as in the <$setfield> 
>>> widgets. The former do not target the value for the target propagated with 
>>> the 'param=' attribute by default, and in some circumstances will, 
>>> therefore, target a different tiddler.
>>>
>>
>> Ok. 
>> Can you give me an example when it won't target the current tiddler or 
>> the tiddler being created? 
>>
>> Cheers Måns Mårtensson
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Måns]

Hi Matabele

Yes it does. Thank you :-)

Cheers Måns Mårtensson

Den lørdag den 31. maj 2014 12.37.11 UTC+2 skrev Matabele:
>
> Hi Mans
>
> The set and setTo attributes of the button and maketid widgets have 
> 'currentTiddler' as the default target. The setfield widget has 
> 'currentTiddler' as the default target only in the absence of a parameter 
> to the calling 'tw-set-field' message and in the absence of a value for the 
> tiddler attribute.
>
> Using the test code -- the setfield widget will target 'Target Two' (the 
> message parameter) whilst the button widget will target 'Target One' 
> ('currentTiddler'.) The set and setTo attributes of the maketid widget 
> function the same way as those of the button widget -- adopting the 
> 'currentTiddler' as the target. Neither the maketid nor the setfield widget 
> change the value of the 'currentTiddler' -- the target must be specified by 
> way of the calling event parameter or with the tiddler attribute (which 
> overrides the calling event param.)
>
> <$tiddler tiddler="Target One">
> <$setfield set="!!text" setTo="this is the text from the setfield widget">
> <$button set="!!text" setTo="this is the text from the button widget" 
> message="tw-set-field" param="Target Two">Test
> 
>
> Hope this clarifies.
>
> regards
>
>
> On Saturday, May 31, 2014 10:26:16 AM UTC+2, Måns wrote:
>>
>> Hi Matabele
>>  
>>
>>> Exercise caution when using the 'set=' and 'setTo=' attributes of the 
>>> <$button> and <$maketid> widgets in the same way as in the <$setfield> 
>>> widgets. The former do not target the value for the target propagated with 
>>> the 'param=' attribute by default, and in some circumstances will, 
>>> therefore, target a different tiddler.
>>>
>>
>> Ok. 
>> Can you give me an example when it won't target the current tiddler or 
>> the tiddler being created? 
>>
>> Cheers Måns Mårtensson
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Matabele]

Hi Mans

I had an additional thought - the following code might appear to 
synchronise the target:

<$tiddler tiddler="Target One">
<$setfield set="!!field3" setTo="this is the text from the setfield widget">
<$maketid title={{!!title}} set="!!field2" setTo="this is text from the 
maketid widget" message="tw-set-field">
<$button set="!!field1" setTo="this is the text from the button widget" 
message="tw-new-tiddler">Test


However this will be so only in the absence of an existing tiddler titled 
'Target One'. If 'Target One' exists, the maketid widget will create 
'Target One 1' which will be targeted by the setfield widget (field3) -- 
however the set and setTo attributes of the button and maketid widgets will 
target the existing 'Tiddler One' (field1 and field2.) 

regards

On Saturday, May 31, 2014 10:26:16 AM UTC+2, Måns wrote:
>
> Hi Matabele
>  
>
>> Exercise caution when using the 'set=' and 'setTo=' attributes of the 
>> <$button> and <$maketid> widgets in the same way as in the <$setfield> 
>> widgets. The former do not target the value for the target propagated with 
>> the 'param=' attribute by default, and in some circumstances will, 
>> therefore, target a different tiddler.
>>
>
> Ok. 
> Can you give me an example when it won't target the current tiddler or the 
> tiddler being created? 
>
> Cheers Måns Mårtensson
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Matabele]

Hi Mans

The set and setTo attributes of the button and maketid widgets have 
'currentTiddler' as the default target. The setfield widget has 
'currentTiddler' as the default target only in the absence of a parameter 
to the calling 'tw-set-field' message and in the absence of a value for the 
tiddler attribute.

Using the test code -- the setfield widget will target 'Target Two' (the 
message parameter) whilst the button widget will target 'Target One' 
('currentTiddler'.) The set and setTo attributes of the maketid widget 
function the same way as those of the button widget -- adopting the 
'currentTiddler' as the target. Neither the maketid nor the setfield widget 
change the value of the 'currentTiddler' -- the target must be specified by 
way of the calling event parameter or with the tiddler attribute (which 
overrides the calling event param.)

<$tiddler tiddler="Target One">
<$setfield set="!!text" setTo="this is the text from the setfield widget">
<$button set="!!text" setTo="this is the text from the button widget" 
message="tw-set-field" param="Target Two">Test


Hope this clarifies.

regards


On Saturday, May 31, 2014 10:26:16 AM UTC+2, Måns wrote:
>
> Hi Matabele
>  
>
>> Exercise caution when using the 'set=' and 'setTo=' attributes of the 
>> <$button> and <$maketid> widgets in the same way as in the <$setfield> 
>> widgets. The former do not target the value for the target propagated with 
>> the 'param=' attribute by default, and in some circumstances will, 
>> therefore, target a different tiddler.
>>
>
> Ok. 
> Can you give me an example when it won't target the current tiddler or the 
> tiddler being created? 
>
> Cheers Måns Mårtensson
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Måns]

Hi Matabele
 

> Exercise caution when using the 'set=' and 'setTo=' attributes of the 
> <$button> and <$maketid> widgets in the same way as in the <$setfield> 
> widgets. The former do not target the value for the target propagated with 
> the 'param=' attribute by default, and in some circumstances will, 
> therefore, target a different tiddler.
>

Ok. 
Can you give me an example when it won't target the current tiddler or the 
tiddler being created? 

Cheers Måns Mårtensson

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Matabele]

Hi Mans

Exercise caution when using the 'set=' and 'setTo=' attributes of the 
<$button> and <$maketid> widgets in the same way as in the <$setfield> 
widgets. The former do not target the value for the target propagated with 
the 'param=' attribute by default, and in some circumstances will, 
therefore, target a different tiddler. 

regards

On Thursday, May 29, 2014 9:55:15 PM UTC+2, Måns wrote:
>
> Hi Matabele
>
> You solved all my problems - Thank you very much :-)
>
> 1) Setting states to fields in current tiddler lets me have individual 
> control with the state of every button in every individual tiddler.
>
>
>
> 2) Your setfield widget makes it possible to set all fields at once.
> My quiz consists of buttons which reveals words when you click on them.
> Now it's possible to open all at once or close all at once :-) GREAT!!
>
> I changed your demo-button and put it in my "song-skeleton/template" like 
> this:
>
> <$reveal type="nomatch" state="!!state1" state="!!state2" state="!!state3" 
> state="!!state4" state="!!state5" state="!!state6" text="show">
> <$setfield set="!!state6" setTo="show">
> <$setfield set="!!state5" setTo="show">
> <$setfield set="!!state4" setTo="show">
> <$setfield set="!!state3" setTo="show">
> <$setfield set="!!state2" setTo="show">
> <$button  set="!!state1" setTo="show" message="tw-set-field">Show all 
> words
> 
> <$reveal type="match" state="!!state1" state="!!state2" state="!!state3" 
> state="!!state4" state="!!state5" state="!!state6" text="show">
> <$setfield set="!!state6" setTo="hide">
> <$setfield set="!!state5" setTo="hide">
> <$setfield set="!!state4" setTo="hide">
> <$setfield set="!!state3" setTo="hide">
> <$setfield set="!!state2" setTo="hide">
> <$button set="!!state1" setTo="hide" message="tw-set-field">Hide all 
> words
> 
>
>
> It was basically a trial/error process on my part - don't know if it could 
> have been written with less code? Point is: IT WORKS :-)
>
> Thank you again Matabele - You saved my day :-)
>
> Cheers Måns Mårtensson
>
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Matabele]

Hi Mans

Glad to be of assistance -- appears you ran into the limitation my widgets 
were designed to address -- the need for one button to initiate several 
actions. In the process of developing a couple of applications I am working 
on, this same limitation kept cropping up. 

regards

On Thursday, May 29, 2014 9:55:15 PM UTC+2, Måns wrote:
>
> Hi Matabele
>
> You solved all my problems - Thank you very much :-)
>
> 1) Setting states to fields in current tiddler lets me have individual 
> control with the state of every button in every individual tiddler.
>
>
>
> 2) Your setfield widget makes it possible to set all fields at once.
> My quiz consists of buttons which reveals words when you click on them.
> Now it's possible to open all at once or close all at once :-) GREAT!!
>
> I changed your demo-button and put it in my "song-skeleton/template" like 
> this:
>
> <$reveal type="nomatch" state="!!state1" state="!!state2" state="!!state3" 
> state="!!state4" state="!!state5" state="!!state6" text="show">
> <$setfield set="!!state6" setTo="show">
> <$setfield set="!!state5" setTo="show">
> <$setfield set="!!state4" setTo="show">
> <$setfield set="!!state3" setTo="show">
> <$setfield set="!!state2" setTo="show">
> <$button  set="!!state1" setTo="show" message="tw-set-field">Show all 
> words
> 
> <$reveal type="match" state="!!state1" state="!!state2" state="!!state3" 
> state="!!state4" state="!!state5" state="!!state6" text="show">
> <$setfield set="!!state6" setTo="hide">
> <$setfield set="!!state5" setTo="hide">
> <$setfield set="!!state4" setTo="hide">
> <$setfield set="!!state3" setTo="hide">
> <$setfield set="!!state2" setTo="hide">
> <$button set="!!state1" setTo="hide" message="tw-set-field">Hide all 
> words
> 
>
>
> It was basically a trial/error process on my part - don't know if it could 
> have been written with less code? Point is: IT WORKS :-)
>
> Thank you again Matabele - You saved my day :-)
>
> Cheers Måns Mårtensson
>
>
> Den torsdag den 29. maj 2014 10.55.20 UTC+2 skrev Matabele:
>>
>> Hi Mans
>>
>> Putting things together -- try this on: http://gwiz.tiddlyspot.com/
>>
>> <$reveal type="nomatch" state="!!state1" text="show">
>> <$fieldset tiddler="other-target"  set="!!text" setTo="2">
>> <$setfield tiddler="target" set="!!text" setTo="your-content">
>> <$button  set="!!state1" setTo="show" 
>> message="tw-set-field">Set
>> 
>> <$reveal type="match" state="!!state1" text="show">
>> <$fieldset tiddler="other-target"  set="!!text" setTo="other-content">
>> <$setfield tiddler="target" set="!!text" setTo="1">
>> <$button set="!!state1" setTo="hide" 
>> message="tw-set-field">Set
>> 
>>
>> regards
>>
>> On Sunday, May 25, 2014 10:38:21 PM UTC+2, Måns wrote:
>>>
>>> Hi TwWizards
>>>
>>> I don't know how to create a "showwhen" field value is *not* a specified 
>>> value with the list filter field operator.
>>>
>>> <$list filter="[mark[1]]"><$view 
>>> field="1"/>
>>> will show the text value of field 1 wrapped in my "red class" when 
>>> there's a text value "1"  of another field "mark". 
>>>
>>> How do I create the opposite effect? - sth like when the value of the 
>>> field "mark" is not 1 - then show value og field one (no class)?
>>>
>>> <$list filter="![mark[1]]"><$view field="1"/>
>>>
>>> Cheers Måns Mårtensson
>>>
>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Måns]

Hi Matabele

I forgot to mention that you also gave me the option to use a new tiddler 
button to create new quizzes with predefined fields (incl. tags): 

<$setfield set="!!skift" setTo="1">
<$setfield set="!!6" setTo="Word 6">
<$setfield set="!!5" setTo="Word 5">
<$setfield set="!!4" setTo="Word 4">
<$setfield set="!!3" setTo="Word 3">
<$setfield set="!!2" setTo="Word 2">
<$setfield set="!!1" setTo="Word 1">
<$setfield set="!!text" setTo="Choose a number. Click on it to reveal a word 
from a verse line. Guess what song it is - or sing another one whych uses that 
exact word." >
<$maketid  title="Sang" tags="sang" edit="show" message="tw-set-field">
<$button message="tw-new-tiddler">New song [img width=16 class="tw-image" 
[$:/favicon.ico]]










Thank you again, again :-)

Cheers Måns Mårtensson

Den torsdag den 29. maj 2014 21.55.15 UTC+2 skrev Måns:
>
> Hi Matabele
>
> You solved all my problems - Thank you very much :-)
>
> 1) Setting states to fields in current tiddler lets me have individual 
> control with the state of every button in every individual tiddler.
>
>
>
> 2) Your setfield widget makes it possible to set all fields at once.
> My quiz consists of buttons which reveals words when you click on them.
> Now it's possible to open all at once or close all at once :-) GREAT!!
>
> I changed your demo-button and put it in my "song-skeleton/template" like 
> this:
>
> <$reveal type="nomatch" state="!!state1" state="!!state2" state="!!state3" 
> state="!!state4" state="!!state5" state="!!state6" text="show">
> <$setfield set="!!state6" setTo="show">
> <$setfield set="!!state5" setTo="show">
> <$setfield set="!!state4" setTo="show">
> <$setfield set="!!state3" setTo="show">
> <$setfield set="!!state2" setTo="show">
> <$button  set="!!state1" setTo="show" message="tw-set-field">Show all 
> words
> 
> <$reveal type="match" state="!!state1" state="!!state2" state="!!state3" 
> state="!!state4" state="!!state5" state="!!state6" text="show">
> <$setfield set="!!state6" setTo="hide">
> <$setfield set="!!state5" setTo="hide">
> <$setfield set="!!state4" setTo="hide">
> <$setfield set="!!state3" setTo="hide">
> <$setfield set="!!state2" setTo="hide">
> <$button set="!!state1" setTo="hide" message="tw-set-field">Hide all 
> words
> 
>
>
> It was basically a trial/error process on my part - don't know if it could 
> have been written with less code? Point is: IT WORKS :-)
>
> Thank you again Matabele - You saved my day :-)
>
> Cheers Måns Mårtensson
>
>
> Den torsdag den 29. maj 2014 10.55.20 UTC+2 skrev Matabele:
>>
>> Hi Mans
>>
>> Putting things together -- try this on: http://gwiz.tiddlyspot.com/
>>
>> <$reveal type="nomatch" state="!!state1" text="show">
>> <$fieldset tiddler="other-target"  set="!!text" setTo="2">
>> <$setfield tiddler="target" set="!!text" setTo="your-content">
>> <$button  set="!!state1" setTo="show" 
>> message="tw-set-field">Set
>> 
>> <$reveal type="match" state="!!state1" text="show">
>> <$fieldset tiddler="other-target"  set="!!text" setTo="other-content">
>> <$setfield tiddler="target" set="!!text" setTo="1">
>> <$button set="!!state1" setTo="hide" 
>> message="tw-set-field">Set
>> 
>>
>> regards
>>
>> On Sunday, May 25, 2014 10:38:21 PM UTC+2, Måns wrote:
>>>
>>> Hi TwWizards
>>>
>>> I don't know how to create a "showwhen" field value is *not* a specified 
>>> value with the list filter field operator.
>>>
>>> <$list filter="[mark[1]]"><$view 
>>> field="1"/>
>>> will show the text value of field 1 wrapped in my "red class" when 
>>> there's a text value "1"  of another field "mark". 
>>>
>>> How do I create the opposite effect? - sth like when the value of the 
>>> field "mark" is not 1 - then show value og field one (no class)?
>>>
>>> <$list filter="![mark[1]]"><$view field="1"/>
>>>
>>> Cheers Måns Mårtensson
>>>
>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Måns]

Hi Matabele

You solved all my problems - Thank you very much :-)

1) Setting states to fields in current tiddler lets me have individual 
control with the state of every button in every individual tiddler.



2) Your setfield widget makes it possible to set all fields at once.
My quiz consists of buttons which reveals words when you click on them.
Now it's possible to open all at once or close all at once :-) GREAT!!

I changed your demo-button and put it in my "song-skeleton/template" like 
this:

<$reveal type="nomatch" state="!!state1" state="!!state2" state="!!state3" 
state="!!state4" state="!!state5" state="!!state6" text="show">
<$setfield set="!!state6" setTo="show">
<$setfield set="!!state5" setTo="show">
<$setfield set="!!state4" setTo="show">
<$setfield set="!!state3" setTo="show">
<$setfield set="!!state2" setTo="show">
<$button  set="!!state1" setTo="show" message="tw-set-field">Show all 
words

<$reveal type="match" state="!!state1" state="!!state2" state="!!state3" 
state="!!state4" state="!!state5" state="!!state6" text="show">
<$setfield set="!!state6" setTo="hide">
<$setfield set="!!state5" setTo="hide">
<$setfield set="!!state4" setTo="hide">
<$setfield set="!!state3" setTo="hide">
<$setfield set="!!state2" setTo="hide">
<$button set="!!state1" setTo="hide" message="tw-set-field">Hide all 
words



It was basically a trial/error process on my part - don't know if it could 
have been written with less code? Point is: IT WORKS :-)

Thank you again Matabele - You saved my day :-)

Cheers Måns Mårtensson


Den torsdag den 29. maj 2014 10.55.20 UTC+2 skrev Matabele:
>
> Hi Mans
>
> Putting things together -- try this on: http://gwiz.tiddlyspot.com/
>
> <$reveal type="nomatch" state="!!state1" text="show">
> <$fieldset tiddler="other-target"  set="!!text" setTo="2">
> <$setfield tiddler="target" set="!!text" setTo="your-content">
> <$button  set="!!state1" setTo="show" 
> message="tw-set-field">Set
> 
> <$reveal type="match" state="!!state1" text="show">
> <$fieldset tiddler="other-target"  set="!!text" setTo="other-content">
> <$setfield tiddler="target" set="!!text" setTo="1">
> <$button set="!!state1" setTo="hide" 
> message="tw-set-field">Set
> 
>
> regards
>
> On Sunday, May 25, 2014 10:38:21 PM UTC+2, Måns wrote:
>>
>> Hi TwWizards
>>
>> I don't know how to create a "showwhen" field value is *not* a specified 
>> value with the list filter field operator.
>>
>> <$list filter="[mark[1]]"><$view 
>> field="1"/>
>> will show the text value of field 1 wrapped in my "red class" when 
>> there's a text value "1"  of another field "mark". 
>>
>> How do I create the opposite effect? - sth like when the value of the 
>> field "mark" is not 1 - then show value og field one (no class)?
>>
>> <$list filter="![mark[1]]"><$view field="1"/>
>>
>> Cheers Måns Mårtensson
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Matabele]

Hi Danielo

On Thursday, May 29, 2014 2:22:19 PM UTC+2, Danielo Rodríguez wrote:

> Hello Matabelle 
>
> I'm still not understanding the need of complicating things. If you want 
> to specify the target tiddler you have an specific parameter called 
> tiddler. Why would you need two things for the same purpose? In TW the !! 
> notation is used for variable substitution. When I read your examples I 
> expect the field name to be substituted for some variable called field1. 
> Maybe you understand it and find it logical but for me is confusing.
>
I wished to maintain a consistent behaviour for 'set=' and setTo=' 
attributes -- this behaviour is borrowed from the <$button> and 
<$linkcatcher> widgets.

For example, if I write: <$button set="field-one" setTo="one">Set 
-- I create a new tiddler titled 'field-one' with a value of 'one' in the 
text field. The correct syntax in this instance is: <$button 
set="!!field-one" setTo="one">Set 

In addition, this allows the <$setfield> widget to be used with this 
syntax: <$setfield set="Target!!field" setTo="value"> -- which targets a 
tiddler other than the default without changing the title of the tiddler 
passed in the parameter attribute. 
 

> Also having the option of construct a stack is nice but make it the only 
> way is a pain. Do you remember the let and set widgets? Which one do you 
> prefer to use? ;-) Would you consider to accept a list of fields and a list 
> of values? Maybe for a different widget?
>

In the case of the <$let> widget, I read somewhere that the widget did not 
interpret the values for the variable to adopt in the same way as the 
<$set> widget - if I remember there were problems with values such as: 
{{!!reference-field}} or perhaps <>. I never tried this, which 
explains my poor memory :-(

The idea of using attributes carrying a list is a good one -- but beyond my 
meagre javascript skills. I am afraid I am restricted pretty much to copy 
and paste of existing code fragments.

I would enjoy a syntax something like: <$setfield 
fields="[field-one:"value1",field-two:"value2",...]">, but I think there 
would be problems when it came round to something like this: <$setfield 
fields="[field-one:"value1",field-two:{{!!some-field}},field-three:<>...]">

If this is possible, then the syntax should be changed, else perhaps, this 
functionality belongs in another widget -- just as the <$set> and <$let> 
widgets each have their appropriate context of use, there would be a case 
here for two widgets.

An alternative is to modify the <$setfield> widget to understand a 
shorthand syntax for simple cases -- whilst keeping the functionality of 
the existing attributes. Something along the lines of:

<$setfield set="field-one" setTo={{!!reference-field}} 
fields="[field-two:"string-two",field-three:"string-three",...]">

I think, perhaps, this unnecessarily confuses things with little saving in 
effort - two separate widgets is probably the way to go.

regards


-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Danielo Rodríguez]

Hello Matabelle 

I'm still not understanding the need of complicating things. If you want to 
specify the target tiddler you have an specific parameter called tiddler. Why 
would you need two things for the same purpose? In TW the !! notation is used 
for variable substitution. When I read your examples I expect the field name to 
be substituted for some variable called field1. Maybe you understand it and 
find it logical but for me is confusing. 

Also having the option of construct a stack is nice but make it the only way is 
a pain. Do you remember the let and set widgets? Which one do you prefer to 
use? ;-) Would you consider to accept a list of fields and a list of values? 
Maybe for a different widget? 

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Matabele]

Hi Mans

I have just updated the <$setfield> widget at: http://gwiz.tiddlyspot.com/ 

This means there is no longer a need to use interspersed fieldset widgets. 
I have added updated code for you to try as a Demo.

regards

On Thursday, May 29, 2014 3:20:21 AM UTC+2, Måns wrote:
>
> Hi TwWizards
>
> A possible workaround for my "button state problem":
>
> How do I make a "reset" button for closing all 6 buttons at once?
> I would be happy with a button which should toggle the text from hide to 
> show in 
> $:/Hit1State, $:/Hit2State, $:/Hit3State, $:/Hit4State, $:/Hit5State 
> and $:/Hit6State - to one/the same state - either show or hide - all at 
> once.
>
> Cheers Måns Mårtensson
>
> Den mandag den 26. maj 2014 00.12.57 UTC+2 skrev Måns:
>>
>> I would also like to be able to set the statevalue of the buttons in 
>> autogenerated systemtiddlers with individual names individually created 
>> from the titles of each quiz sentence/tiddler...
>>
>> eg: "$:/Hit1State" should be sth. like "$:/Hit1StateTiddlerTitle"...
>>
>> If I can't do this all words in button 1 in every tiddler will get 
>> revealed when I click one of them - and I can't have them all open at the 
>> same time eg in a substory list ...
>>
>> 
>>
>>
>> Den søndag den 25. maj 2014 23.44.12 UTC+2 skrev Måns:
>>>
>>> Hi cmari
>>>
>>> I want to create a quiz battle between two teams, where one team chooses 
>>> a number/button - the teacher clicks it - and a word from a full sentence 
>>> gets revealed. 
>>> If the word isn't red the team will try to guess/remember the full 
>>> sentence.
>>> If the word is red - the other team will have a go at it - or choose yet 
>>> another number/button...
>>>
>>> When I set up the quiz I want to be able to choose which field value is 
>>> formatted as red text.
>>>
>>>
>>> My attempt http://hitsang.tiddlyspot.com
>>>
>>> Here "mark" is "skift"
>>>
>>> As you can see :
>>> <$list filter="[skift[1]]"><$view 
>>> field="1"/><$list filter="[!skift[1]]"><$view 
>>> field="1"/>
>>>
>>> shows both versions of the text value of the field "skift" (both black 
>>> and red) - and if you set the value of the field "skift" to anything other 
>>> than "1" - the text is hidden...
>>>
>>> There must be something wrong somewhere ...?
>>>
>>> Cheers Måns Mårtensson
>>>
>>> Den søndag den 25. maj 2014 23.21.11 UTC+2 skrev cmari:

 Hi 

 Hi Måns,
 Maybe I don't understand what you're doing, but the following seemed to 
 work for me:

 <$list filter="[!mark[1]]"><$view field="1"/>
 cmari


 On Sunday, May 25, 2014 2:11:33 PM UTC-7, Måns wrote:
>
> <$list filter="[!field:mark[1]]"><$view field="1"/> also 
> doesn't work...
> I expected that it would show the text value of my field "1" if the 
> field "mark" had another value than "1"...
>
> Cheers
>
> Den søndag den 25. maj 2014 22.42.36 UTC+2 skrev Måns:
>>
>> Made a typo - sorry
>>  
>>
>>> How do I create the opposite effect? - sth like when the value of 
>>> the field "mark" is not 1 - then show value og field one (no class)?
>>>
>>
>> should have been:
>>
>> How do I create the opposite effect? - sth like when the value of the 
>> field "mark" is not 1 - then show value of field one (no class)?
>>
>> <$list filter="![mark[1]]"><$view field="1"/> (doesn't work)
>>
>> Cheers Måns Mårtensson 
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Matabele]

Hi Danielo

I often specify the title of the tiddler and the field -- as in: 
set="Target!!field-one" (this will override any default target - often 
'currentTiddler'.)

I prefer to maintain this standard convention for text references.

regards

On Thursday, May 29, 2014 12:24:59 PM UTC+2, Danielo Rodríguez wrote:
>
> Hello Matabelle, 
>
> Why do you use set="!!field2" instead of just the name of the field? 
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Danielo Rodríguez]

Hello Matabelle, 

Why do you use set="!!field2" instead of just the name of the field? 

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Matabele]

Hi Mans

Putting things together -- try this on: http://gwiz.tiddlyspot.com/

<$reveal type="nomatch" state="!!state1" text="show">
<$fieldset tiddler="other-target"  set="!!text" setTo="2">
<$setfield tiddler="target" set="!!text" setTo="your-content">
<$button  set="!!state1" setTo="show" 
message="tw-set-field">Set

<$reveal type="match" state="!!state1" text="show">
<$fieldset tiddler="other-target"  set="!!text" setTo="other-content">
<$setfield tiddler="target" set="!!text" setTo="1">
<$button set="!!state1" setTo="hide" 
message="tw-set-field">Set


regards

On Sunday, May 25, 2014 10:38:21 PM UTC+2, Måns wrote:
>
> Hi TwWizards
>
> I don't know how to create a "showwhen" field value is *not* a specified 
> value with the list filter field operator.
>
> <$list filter="[mark[1]]"><$view 
> field="1"/>
> will show the text value of field 1 wrapped in my "red class" when there's 
> a text value "1"  of another field "mark". 
>
> How do I create the opposite effect? - sth like when the value of the 
> field "mark" is not 1 - then show value og field one (no class)?
>
> <$list filter="![mark[1]]"><$view field="1"/>
>
> Cheers Måns Mårtensson
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Matabele]

Hi Mans

Looking at your code -- perhaps use fields for your state variables to 
avoid unnecessary proliferation of $:/state tiddlers -- like this:

<$reveal type="nomatch" state="!!Hit1State" text="show">
<$button set="!!Hit1State" setTo="show">O

<$reveal type="match" state="!!Hit1State" text="show">
<$button set="!!Hit1State" setTo="hide">X


regards

On Sunday, May 25, 2014 10:38:21 PM UTC+2, Måns wrote:
>
> Hi TwWizards
>
> I don't know how to create a "showwhen" field value is *not* a specified 
> value with the list filter field operator.
>
> <$list filter="[mark[1]]"><$view 
> field="1"/>
> will show the text value of field 1 wrapped in my "red class" when there's 
> a text value "1"  of another field "mark". 
>
> How do I create the opposite effect? - sth like when the value of the 
> field "mark" is not 1 - then show value og field one (no class)?
>
> <$list filter="![mark[1]]"><$view field="1"/>
>
> Cheers Måns Mårtensson
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Matabele]

Hi

Sorry, that should be (missed a trailing '>'):

<$fieldset tiddler="other-target"  set="!!text" setTo="other-content">
<$setfield tiddler="target" set="!!text" setTo="your-content">
<$button message="tw-set-field">Set

regards

On Thursday, May 29, 2014 9:04:52 AM UTC+2, Matabele wrote:
>
> Hi Mans
>
> Don't know exactly what you need, but my <$setfield> widget was designed 
> to fill the requirement to do several things with one button -- you can try 
> it our here: http://gwiz.tiddlyspot.com/
>
> One suggestion is to re-write the 'text' field with:
>
> ...
> <$fieldset tiddler="other-target"  set="!!text" setTo="other-content"
> <$setfield tiddler="target" set="!!text" setTo="your-content">
> <$button message="tw-set-field">Set
> 
> 
> ...
>
> The widgets can be stacked to set a field of several tiddlers (and/or to 
> set several fields of one tiddler), with one button.
>
> regards
>   
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Matabele]

Hi Mans

Don't know exactly what you need, but my <$setfield> widget was designed to 
fill the requirement to do several things with one button -- you can try it 
our here: http://gwiz.tiddlyspot.com/

One suggestion is to re-write the 'text' field with:

...
<$fieldset tiddler="other-target"  set="!!text" setTo="other-content"
<$setfield tiddler="target" set="!!text" setTo="your-content">
<$button message="tw-set-field">Set


...

The widgets can be stacked to set a field of several tiddlers (and/or to 
set several fields of one tiddler), with one button.

regards
 

On Thursday, May 29, 2014 3:20:21 AM UTC+2, Måns wrote:
>
> Hi TwWizards
>
> A possible workaround for my "button state problem":
>
> How do I make a "reset" button for closing all 6 buttons at once?
> I would be happy with a button which should toggle the text from hide to 
> show in 
> $:/Hit1State, $:/Hit2State, $:/Hit3State, $:/Hit4State, $:/Hit5State 
> and $:/Hit6State - to one/the same state - either show or hide - all at 
> once.
>
> Cheers Måns Mårtensson
>
> Den mandag den 26. maj 2014 00.12.57 UTC+2 skrev Måns:
>>
>> I would also like to be able to set the statevalue of the buttons in 
>> autogenerated systemtiddlers with individual names individually created 
>> from the titles of each quiz sentence/tiddler...
>>
>> eg: "$:/Hit1State" should be sth. like "$:/Hit1StateTiddlerTitle"...
>>
>> If I can't do this all words in button 1 in every tiddler will get 
>> revealed when I click one of them - and I can't have them all open at the 
>> same time eg in a substory list ...
>>
>> 
>>
>>
>> Den søndag den 25. maj 2014 23.44.12 UTC+2 skrev Måns:
>>>
>>> Hi cmari
>>>
>>> I want to create a quiz battle between two teams, where one team chooses 
>>> a number/button - the teacher clicks it - and a word from a full sentence 
>>> gets revealed. 
>>> If the word isn't red the team will try to guess/remember the full 
>>> sentence.
>>> If the word is red - the other team will have a go at it - or choose yet 
>>> another number/button...
>>>
>>> When I set up the quiz I want to be able to choose which field value is 
>>> formatted as red text.
>>>
>>>
>>> My attempt http://hitsang.tiddlyspot.com
>>>
>>> Here "mark" is "skift"
>>>
>>> As you can see :
>>> <$list filter="[skift[1]]"><$view 
>>> field="1"/><$list filter="[!skift[1]]"><$view 
>>> field="1"/>
>>>
>>> shows both versions of the text value of the field "skift" (both black 
>>> and red) - and if you set the value of the field "skift" to anything other 
>>> than "1" - the text is hidden...
>>>
>>> There must be something wrong somewhere ...?
>>>
>>> Cheers Måns Mårtensson
>>>
>>> Den søndag den 25. maj 2014 23.21.11 UTC+2 skrev cmari:

 Hi 

 Hi Måns,
 Maybe I don't understand what you're doing, but the following seemed to 
 work for me:

 <$list filter="[!mark[1]]"><$view field="1"/>
 cmari


 On Sunday, May 25, 2014 2:11:33 PM UTC-7, Måns wrote:
>
> <$list filter="[!field:mark[1]]"><$view field="1"/> also 
> doesn't work...
> I expected that it would show the text value of my field "1" if the 
> field "mark" had another value than "1"...
>
> Cheers
>
> Den søndag den 25. maj 2014 22.42.36 UTC+2 skrev Måns:
>>
>> Made a typo - sorry
>>  
>>
>>> How do I create the opposite effect? - sth like when the value of 
>>> the field "mark" is not 1 - then show value og field one (no class)?
>>>
>>
>> should have been:
>>
>> How do I create the opposite effect? - sth like when the value of the 
>> field "mark" is not 1 - then show value of field one (no class)?
>>
>> <$list filter="![mark[1]]"><$view field="1"/> (doesn't work)
>>
>> Cheers Måns Mårtensson 
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Måns]

Hi TwWizards

A possible workaround for my "button state problem":

How do I make a "reset" button for closing all 6 buttons at once?
I would be happy with a button which should toggle the text from hide to 
show in 
$:/Hit1State, $:/Hit2State, $:/Hit3State, $:/Hit4State, $:/Hit5State 
and $:/Hit6State - to one/the same state - either show or hide - all at 
once.

Cheers Måns Mårtensson

Den mandag den 26. maj 2014 00.12.57 UTC+2 skrev Måns:
>
> I would also like to be able to set the statevalue of the buttons in 
> autogenerated systemtiddlers with individual names individually created 
> from the titles of each quiz sentence/tiddler...
>
> eg: "$:/Hit1State" should be sth. like "$:/Hit1StateTiddlerTitle"...
>
> If I can't do this all words in button 1 in every tiddler will get 
> revealed when I click one of them - and I can't have them all open at the 
> same time eg in a substory list ...
>
> 
>
>
> Den søndag den 25. maj 2014 23.44.12 UTC+2 skrev Måns:
>>
>> Hi cmari
>>
>> I want to create a quiz battle between two teams, where one team chooses 
>> a number/button - the teacher clicks it - and a word from a full sentence 
>> gets revealed. 
>> If the word isn't red the team will try to guess/remember the full 
>> sentence.
>> If the word is red - the other team will have a go at it - or choose yet 
>> another number/button...
>>
>> When I set up the quiz I want to be able to choose which field value is 
>> formatted as red text.
>>
>>
>> My attempt http://hitsang.tiddlyspot.com
>>
>> Here "mark" is "skift"
>>
>> As you can see :
>> <$list filter="[skift[1]]"><$view 
>> field="1"/><$list filter="[!skift[1]]"><$view 
>> field="1"/>
>>
>> shows both versions of the text value of the field "skift" (both black 
>> and red) - and if you set the value of the field "skift" to anything other 
>> than "1" - the text is hidden...
>>
>> There must be something wrong somewhere ...?
>>
>> Cheers Måns Mårtensson
>>
>> Den søndag den 25. maj 2014 23.21.11 UTC+2 skrev cmari:
>>>
>>> Hi 
>>>
>>> Hi Måns,
>>> Maybe I don't understand what you're doing, but the following seemed to 
>>> work for me:
>>>
>>> <$list filter="[!mark[1]]"><$view field="1"/>
>>> cmari
>>>
>>>
>>> On Sunday, May 25, 2014 2:11:33 PM UTC-7, Måns wrote:

 <$list filter="[!field:mark[1]]"><$view field="1"/> also 
 doesn't work...
 I expected that it would show the text value of my field "1" if the 
 field "mark" had another value than "1"...

 Cheers

 Den søndag den 25. maj 2014 22.42.36 UTC+2 skrev Måns:
>
> Made a typo - sorry
>  
>
>> How do I create the opposite effect? - sth like when the value of the 
>> field "mark" is not 1 - then show value og field one (no class)?
>>
>
> should have been:
>
> How do I create the opposite effect? - sth like when the value of the 
> field "mark" is not 1 - then show value of field one (no class)?
>
> <$list filter="![mark[1]]"><$view field="1"/> (doesn't work)
>
> Cheers Måns Mårtensson 
>


-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Måns]

Hi Danielo

http://hitsang.tiddlyspot.com 

Cheers Måns Mårtensson

Den tirsdag den 27. maj 2014 12.50.43 UTC+2 skrev Danielo Rodríguez:
>
> Hello. 
>
> When you have a working example could you share? I liked the 
> implementation but I didn't understand the use case. Maybe a real example 
> could help me. 
>
> Thank you! 
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Danielo Rodríguez]

Hello. 

When you have a working example could you share? I liked the implementation but 
I didn't understand the use case. Maybe a real example could help me. 

Thank you! 

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Måns]

Hi Alberto

Maybe it will work If I wrap a   in  <$list 
> filter="[!fieldname[empty/no text value]]"/> 
> like this: <$list filter="[tag[sang]!1[]]"><$button><$view 
> field="1"/>  ??
>

It actually worked :-D 

I had to insert is[current] in every list definition to make the template 
work pr. tiddler as it should.

I still need to be able to set different states on the buttons - or else I 
can't have several sentences open at the same time. 
Accidentally showing the contents of buttons in other quizzes would not be 
good - unless you want to finish the quiz very quickly - of course ...

Cheers Måns Mårtensson

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Måns]

Hi Alberto

I looked at 
http://hitsang.tiddlyspot.com
 
>
> It's cool. I'm impressed. 
>

Thanks. Glad you like it. :-)

I wonder - do you know how I would hide columns in the (invisible) table 
depending on if there's a value for the field used to show text, when 
hitting a button?

I will use a skeleton for creating new tiddlers wich has predefined empty 
fields (1, 2, 3, 4, 5 and 6) . If a field is empty I would like to hide the 
corresponding column - and the button in it... 

Maybe it will work If I wrap a   in  <$list 
filter="[!fieldname[empty/no text value]]"/> 
like this: <$list filter="[tag[sang]!1[]]"><$button><$view 
field="1"/>  ??

I assume that you do things like that (hide elements based on whether there 
are named fields and/or field values) in your Tesis tw5 on TiddlySpot?

Cheers Måns Mårtensson
 

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Alberto Molina]

Hi Måns, 

I looked at http://hitsang.tiddlyspot.com

It's cool. I'm impressed. 

Alberto

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Måns]

Aaah - Yes it did

Thanks a lot cmari - Great  :-)

Cheers Måns Mårtensson

Den mandag den 26. maj 2014 00.05.48 UTC+2 skrev cmari:
>
> Does it help to tag to the filter?
> <$list filter="[tag[sang]skift[1]]"><$view 
> field="1"/><$list filter="[tag[sang]!skift[1]]"><$view 
> field="1"/>
>
> On Sunday, May 25, 2014 2:44:12 PM UTC-7, Måns wrote:
>>
>> Hi cmari
>>
>> I want to create a quiz battle between two teams, where one team chooses 
>> a number/button - the teacher clicks it - and a word from a full sentence 
>> gets revealed. 
>> If the word isn't red the team will try to guess/remember the full 
>> sentence.
>> If the word is red - the other team will have a go at it - or choose yet 
>> another number/button...
>>
>> When I set up the quiz I want to be able to choose which field value is 
>> formatted as red text.
>>
>>
>> My attempt http://hitsang.tiddlyspot.com
>>
>> Here "mark" is "skift"
>>
>> As you can see :
>> <$list filter="[skift[1]]"><$view 
>> field="1"/><$list filter="[!skift[1]]"><$view 
>> field="1"/>
>>
>> shows both versions of the text value of the field "skift" (both black 
>> and red) - and if you set the value of the field "skift" to anything other 
>> than "1" - the text is hidden...
>>
>> There must be something wrong somewhere ...?
>>
>> Cheers Måns Mårtensson
>>
>> Den søndag den 25. maj 2014 23.21.11 UTC+2 skrev cmari:
>>>
>>> Hi 
>>>
>>> Hi Måns,
>>> Maybe I don't understand what you're doing, but the following seemed to 
>>> work for me:
>>>
>>> <$list filter="[!mark[1]]"><$view field="1"/>
>>> cmari
>>>
>>>
>>> On Sunday, May 25, 2014 2:11:33 PM UTC-7, Måns wrote:

 <$list filter="[!field:mark[1]]"><$view field="1"/> also 
 doesn't work...
 I expected that it would show the text value of my field "1" if the 
 field "mark" had another value than "1"...

 Cheers

 Den søndag den 25. maj 2014 22.42.36 UTC+2 skrev Måns:
>
> Made a typo - sorry
>  
>
>> How do I create the opposite effect? - sth like when the value of the 
>> field "mark" is not 1 - then show value og field one (no class)?
>>
>
> should have been:
>
> How do I create the opposite effect? - sth like when the value of the 
> field "mark" is not 1 - then show value of field one (no class)?
>
> <$list filter="![mark[1]]"><$view field="1"/> (doesn't work)
>
> Cheers Måns Mårtensson 
>


-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Måns]

I would also like to be able to set the statevalue of the buttons in 
autogenerated systemtiddlers with individual names individually created 
from the titles of each quiz sentence/tiddler...

eg: "$:/Hit1State" should be sth. like "$:/Hit1StateTiddlerTitle"...

If I can't do this all words in button 1 in every tiddler will get revealed 
when I click one of them - and I can't have them all open at the same time 
eg in a substory list ...




Den søndag den 25. maj 2014 23.44.12 UTC+2 skrev Måns:
>
> Hi cmari
>
> I want to create a quiz battle between two teams, where one team chooses a 
> number/button - the teacher clicks it - and a word from a full sentence 
> gets revealed. 
> If the word isn't red the team will try to guess/remember the full 
> sentence.
> If the word is red - the other team will have a go at it - or choose yet 
> another number/button...
>
> When I set up the quiz I want to be able to choose which field value is 
> formatted as red text.
>
>
> My attempt http://hitsang.tiddlyspot.com
>
> Here "mark" is "skift"
>
> As you can see :
> <$list filter="[skift[1]]"><$view 
> field="1"/><$list filter="[!skift[1]]"><$view 
> field="1"/>
>
> shows both versions of the text value of the field "skift" (both black and 
> red) - and if you set the value of the field "skift" to anything other than 
> "1" - the text is hidden...
>
> There must be something wrong somewhere ...?
>
> Cheers Måns Mårtensson
>
> Den søndag den 25. maj 2014 23.21.11 UTC+2 skrev cmari:
>>
>> Hi 
>>
>> Hi Måns,
>> Maybe I don't understand what you're doing, but the following seemed to 
>> work for me:
>>
>> <$list filter="[!mark[1]]"><$view field="1"/>
>> cmari
>>
>>
>> On Sunday, May 25, 2014 2:11:33 PM UTC-7, Måns wrote:
>>>
>>> <$list filter="[!field:mark[1]]"><$view field="1"/> also doesn't 
>>> work...
>>> I expected that it would show the text value of my field "1" if the 
>>> field "mark" had another value than "1"...
>>>
>>> Cheers
>>>
>>> Den søndag den 25. maj 2014 22.42.36 UTC+2 skrev Måns:

 Made a typo - sorry
  

> How do I create the opposite effect? - sth like when the value of the 
> field "mark" is not 1 - then show value og field one (no class)?
>

 should have been:

 How do I create the opposite effect? - sth like when the value of the 
 field "mark" is not 1 - then show value of field one (no class)?

 <$list filter="![mark[1]]"><$view field="1"/> (doesn't work)

 Cheers Måns Mårtensson 

>>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[cmari]

sorry, typo: Does it help to *add a* tag to the filter?
<$list filter="[tag[sang]skift[1]]"><
span class="red"><$view field="1"/><$list 
filter="[tag[sang]!skift[1]]"><$view field="1"/>

On Sunday, May 25, 2014 3:05:48 PM UTC-7, cmari wrote:
>
> Does it help to tag to the filter?
> <$list filter="[tag[sang]skift[1]]"><$view 
> field="1"/><$list filter="[tag[sang]!skift[1]]"><$view 
> field="1"/>
>
> On Sunday, May 25, 2014 2:44:12 PM UTC-7, Måns wrote:
>>
>> Hi cmari
>>
>> I want to create a quiz battle between two teams, where one team chooses 
>> a number/button - the teacher clicks it - and a word from a full sentence 
>> gets revealed. 
>> If the word isn't red the team will try to guess/remember the full 
>> sentence.
>> If the word is red - the other team will have a go at it - or choose yet 
>> another number/button...
>>
>> When I set up the quiz I want to be able to choose which field value is 
>> formatted as red text.
>>
>>
>> My attempt http://hitsang.tiddlyspot.com
>>
>> Here "mark" is "skift"
>>
>> As you can see :
>> <$list filter="[skift[1]]"><$view 
>> field="1"/><$list filter="[!skift[1]]"><$view 
>> field="1"/>
>>
>> shows both versions of the text value of the field "skift" (both black 
>> and red) - and if you set the value of the field "skift" to anything other 
>> than "1" - the text is hidden...
>>
>> There must be something wrong somewhere ...?
>>
>> Cheers Måns Mårtensson
>>
>> Den søndag den 25. maj 2014 23.21.11 UTC+2 skrev cmari:
>>>
>>> Hi 
>>>
>>> Hi Måns,
>>> Maybe I don't understand what you're doing, but the following seemed to 
>>> work for me:
>>>
>>> <$list filter="[!mark[1]]"><$view field="1"/>
>>> cmari
>>>
>>>
>>> On Sunday, May 25, 2014 2:11:33 PM UTC-7, Måns wrote:

 <$list filter="[!field:mark[1]]"><$view field="1"/> also 
 doesn't work...
 I expected that it would show the text value of my field "1" if the 
 field "mark" had another value than "1"...

 Cheers

 Den søndag den 25. maj 2014 22.42.36 UTC+2 skrev Måns:
>
> Made a typo - sorry
>  
>
>> How do I create the opposite effect? - sth like when the value of the 
>> field "mark" is not 1 - then show value og field one (no class)?
>>
>
> should have been:
>
> How do I create the opposite effect? - sth like when the value of the 
> field "mark" is not 1 - then show value of field one (no class)?
>
> <$list filter="![mark[1]]"><$view field="1"/> (doesn't work)
>
> Cheers Måns Mårtensson 
>


-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[cmari]

Does it help to tag to the filter?
<$list filter="[tag[sang]skift[1]]"><$view 
field="1"/><$list filter="[tag[sang]!skift[1]]"><$view 
field="1"/>

On Sunday, May 25, 2014 2:44:12 PM UTC-7, Måns wrote:
>
> Hi cmari
>
> I want to create a quiz battle between two teams, where one team chooses a 
> number/button - the teacher clicks it - and a word from a full sentence 
> gets revealed. 
> If the word isn't red the team will try to guess/remember the full 
> sentence.
> If the word is red - the other team will have a go at it - or choose yet 
> another number/button...
>
> When I set up the quiz I want to be able to choose which field value is 
> formatted as red text.
>
>
> My attempt http://hitsang.tiddlyspot.com
>
> Here "mark" is "skift"
>
> As you can see :
> <$list filter="[skift[1]]"><$view 
> field="1"/><$list filter="[!skift[1]]"><$view 
> field="1"/>
>
> shows both versions of the text value of the field "skift" (both black and 
> red) - and if you set the value of the field "skift" to anything other than 
> "1" - the text is hidden...
>
> There must be something wrong somewhere ...?
>
> Cheers Måns Mårtensson
>
> Den søndag den 25. maj 2014 23.21.11 UTC+2 skrev cmari:
>>
>> Hi 
>>
>> Hi Måns,
>> Maybe I don't understand what you're doing, but the following seemed to 
>> work for me:
>>
>> <$list filter="[!mark[1]]"><$view field="1"/>
>> cmari
>>
>>
>> On Sunday, May 25, 2014 2:11:33 PM UTC-7, Måns wrote:
>>>
>>> <$list filter="[!field:mark[1]]"><$view field="1"/> also doesn't 
>>> work...
>>> I expected that it would show the text value of my field "1" if the 
>>> field "mark" had another value than "1"...
>>>
>>> Cheers
>>>
>>> Den søndag den 25. maj 2014 22.42.36 UTC+2 skrev Måns:

 Made a typo - sorry
  

> How do I create the opposite effect? - sth like when the value of the 
> field "mark" is not 1 - then show value og field one (no class)?
>

 should have been:

 How do I create the opposite effect? - sth like when the value of the 
 field "mark" is not 1 - then show value of field one (no class)?

 <$list filter="![mark[1]]"><$view field="1"/> (doesn't work)

 Cheers Måns Mårtensson 

>>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Måns]

Hi cmari

I want to create a quiz battle between two teams, where one team chooses a 
number/button - the teacher clicks it - and a word from a full sentence 
gets revealed. 
If the word isn't red the team will try to guess/remember the full sentence.
If the word is red - the other team will have a go at it - or choose yet 
another number/button...

When I set up the quiz I want to be able to choose which field value is 
formatted as red text.


My attempt http://hitsang.tiddlyspot.com

Here "mark" is "skift"

As you can see :
<$list filter="[skift[1]]"><$view 
field="1"/><$list filter="[!skift[1]]"><$view 
field="1"/>

shows both versions of the text value of the field "skift" (both black and 
red) - and if you set the value of the field "skift" to anything other than 
"1" - the text is hidden...

There must be something wrong somewhere ...?

Cheers Måns Mårtensson

Den søndag den 25. maj 2014 23.21.11 UTC+2 skrev cmari:
>
> Hi 
>
> Hi Måns,
> Maybe I don't understand what you're doing, but the following seemed to 
> work for me:
>
> <$list filter="[!mark[1]]"><$view field="1"/>
> cmari
>
>
> On Sunday, May 25, 2014 2:11:33 PM UTC-7, Måns wrote:
>>
>> <$list filter="[!field:mark[1]]"><$view field="1"/> also doesn't 
>> work...
>> I expected that it would show the text value of my field "1" if the field 
>> "mark" had another value than "1"...
>>
>> Cheers
>>
>> Den søndag den 25. maj 2014 22.42.36 UTC+2 skrev Måns:
>>>
>>> Made a typo - sorry
>>>  
>>>
 How do I create the opposite effect? - sth like when the value of the 
 field "mark" is not 1 - then show value og field one (no class)?

>>>
>>> should have been:
>>>
>>> How do I create the opposite effect? - sth like when the value of the 
>>> field "mark" is not 1 - then show value of field one (no class)?
>>>
>>> <$list filter="![mark[1]]"><$view field="1"/> (doesn't work)
>>>
>>> Cheers Måns Mårtensson 
>>>
>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[cmari]

Hi 

Hi Måns,
Maybe I don't understand what you're doing, but the following seemed to 
work for me:

<$list filter="[!mark[1]]"><$view field="1"/>
cmari


On Sunday, May 25, 2014 2:11:33 PM UTC-7, Måns wrote:
>
> <$list filter="[!field:mark[1]]"><$view field="1"/> also doesn't 
> work...
> I expected that it would show the text value of my field "1" if the field 
> "mark" had another value than "1"...
>
> Cheers
>
> Den søndag den 25. maj 2014 22.42.36 UTC+2 skrev Måns:
>>
>> Made a typo - sorry
>>  
>>
>>> How do I create the opposite effect? - sth like when the value of the 
>>> field "mark" is not 1 - then show value og field one (no class)?
>>>
>>
>> should have been:
>>
>> How do I create the opposite effect? - sth like when the value of the 
>> field "mark" is not 1 - then show value of field one (no class)?
>>
>> <$list filter="![mark[1]]"><$view field="1"/> (doesn't work)
>>
>> Cheers Måns Mårtensson 
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Måns]

<$list filter="[!field:mark[1]]"><$view field="1"/> also doesn't 
work...
I expected that it would show the text value of my field "1" if the field 
"mark" had another value than "1"...

Cheers

Den søndag den 25. maj 2014 22.42.36 UTC+2 skrev Måns:
>
> Made a typo - sorry
>  
>
>> How do I create the opposite effect? - sth like when the value of the 
>> field "mark" is not 1 - then show value og field one (no class)?
>>
>
> should have been:
>
> How do I create the opposite effect? - sth like when the value of the 
> field "mark" is not 1 - then show value of field one (no class)?
>
> <$list filter="![mark[1]]"><$view field="1"/> (doesn't work)
>
> Cheers Måns Mårtensson 
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5]list filter field !value question

[Måns]

Made a typo - sorry
 

> How do I create the opposite effect? - sth like when the value of the 
> field "mark" is not 1 - then show value og field one (no class)?
>

should have been:

How do I create the opposite effect? - sth like when the value of the field 
"mark" is not 1 - then show value of field one (no class)?

<$list filter="![mark[1]]"><$view field="1"/> (doesn't work)

Cheers Måns Mårtensson 

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.