[tw] Re: [TW5] The $maketid and $setfield widgets

2014-07-17 Thread Matabele
Hi

An option was introduced, in version 5.0.13-beta, to delimit the value 
specified in an attribute to a widget between triple quotes. This turns out 
to be extremely useful, in particular when creating a new tiddler from 
scratch -- as in the 'Stacked Widgets' example.

It is now possible, not only to retain the formatting of the wikitext to 
which the text field will be set, but also to include code (such as an 
enclosed widget button), within this value. 

Take a look at the example at the bottom of the 'Stacked Widgets' tiddler 
at: http://gwiz.tiddlyspot.com

regards

On Tuesday, May 27, 2014 10:01:10 AM UTC+2, Matabele wrote:

 Hi 

 I have been working on a couple of widget plugins which address problems I 
 was having when developing TW5 applications -- they may be found here: 
 http://gwiz.tiddlyspot.com

 The $setfield widget was my response to the need to initiate more than 
 one function with one button. Starting out with a mechanism borrowed from 
 the linkcatcher widget, I developed a pair of complementary widgets that 
 could be assembled in a stack around a button widget -- the title of the 
 target widget being passed through the stack with an event parameter.

 The $maketid widget was my response to the spurious javascript errors I 
 was experiencing with the $newtiddler widget. My efforts to address the 
 error by modifying the $newtiddler widget failed, and I resorted to 
 rewriting the widget by adopting the mechanism borrowed from the 
 linkcatcher widget. This appears to have cured the bad behaviour of the 
 $newtiddler widget, at least in the context in which I was experiencing 
 problems.

 I have constructed the widgets in such a way that they may be used 
 together in the same stack. Other widgets could be developed using the same 
 mechanism which could then be added to the widget stack (the 
 $fieldmangler and $linkcatcher widgets are partially compatible.)

 I would welcome any feedback with respect the concept of the widgets, and 
 any ideas with respect modifying the code to broaden the context of their 
 application.

 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] The $maketid and $setfield widgets

2014-06-03 Thread cmari
Thanks for creating widgets to do exactly what I'd been puzzling over!  One 
thing I still can't figure out: Is is possible to create a single button 
that simultaneously:
1. sets field info AND
2. removes a (specified) tag?
Thanks!
cmari

-- 
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] The $maketid and $setfield widgets

2014-06-03 Thread cmari
Knowing that it was possible gave me the fortitude to continue with my 
trial-and-error flailing!
I still don't quite understand the pattern for which macro to use first and 
when to add which message where, but in case it's helpful for someone else, 
here's my working solution to accomplish the following with a single button:
1. set a field
2. set another field
3. add one tag
4. remove another

$setfield set=!!field1 setTo=value1
$setfield set=!!field2 setTo=value2
$mangletags find=oldtag message=tw-set-field
$mangletags add=newtag
$button message=tw-mangle-tagsbutton text here/$button
/$mangletags/$mangletags/$setfield/$setfield

(I haven't included a target because I put this in a tiddler called 
MyButton and then use it inside other tiddlers, e.g., {{!!title||MyButton}} 
)

This is really helpful - thanks!
cmari

On Tuesday, June 3, 2014 8:42:20 AM UTC-7, Matabele wrote:

 Hi cmari

 Yes -- using the $setfield and $mangletags widgets available here: 
 http://gwiz.tiddlyspot.com/

 $mangletags find=tag-to-remove
 $setfield set=!!field-to-set setTo=value-for-field 
 message=tw-mangle-tags
 $button message=tw-set-field param=target-tiddlerSet/$button
 /$setfield/$mangletags

 Have a look at the Demos on the site -- the code should give you some 
 ideas on how to use the widgets. The 'Another Demo', in particular, does 
 something similar to your needs.


 On Tuesday, June 3, 2014 5:26:24 PM UTC+2, cmari wrote:

 Thanks for creating widgets to do exactly what I'd been puzzling over!  
 One thing I still can't figure out: Is is possible to create a single 
 button that simultaneously:
 1. sets field info AND
 2. removes a (specified) tag?
 Thanks!
 cmari



-- 
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] The $maketid and $setfield widgets

2014-06-03 Thread Matabele
Hi cmari

I don't know what you are trying to achieve, but there's also a 'find and 
replace' option for the $mangletags widget. Your code using two widgets 
will add 'newtag' regardless of whether the tiddler was previously tagged 
with 'oldtag' -- with the find and replace option, 'newtag' will be added 
only to those tiddlers that were previously tagged 'oldtag'.

The syntax in this case: $mangletags find=oldtag add=newtag 

The widgets may be used in any order -- however, the default behaviour in 
most cases is to pass on the received message to the next widget in the 
stack. it is easier, therefore, to stack widgets of the same type adjacent 
to one another -- changing the message only when the widget type changes 
(as you have done.) The $maketid widget is the exception, as the 
parameter caught by the widget becomes the default for the template 
(maintaining compatibility with the standard 'tw-new-tiddler' message) -- 
and the generated parameter is set to the value of the 'title' attribute. 
All of the other widgets pass on the title of the target tiddler as the 
parameter to the message by default (unless changed with 'param='), and 
pass on the same message by default (unless changed with 'message='.)

Hope this better explains how to use the widgets.

regards

On Tuesday, June 3, 2014 7:33:28 PM UTC+2, cmari wrote:

 Knowing that it was possible gave me the fortitude to continue with my 
 trial-and-error flailing!
 I still don't quite understand the pattern for which macro to use first 
 and when to add which message where, but in case it's helpful for someone 
 else, here's my working solution to accomplish the following with a single 
 button:
 1. set a field
 2. set another field
 3. add one tag
 4. remove another

 $setfield set=!!field1 setTo=value1
 $setfield set=!!field2 setTo=value2
 $mangletags find=oldtag message=tw-set-field
 $mangletags add=newtag
 $button message=tw-mangle-tagsbutton text here/$button
 /$mangletags/$mangletags/$setfield/$setfield

 (I haven't included a target because I put this in a tiddler called 
 MyButton and then use it inside other tiddlers, e.g., {{!!title||MyButton}} 
 )

 This is really helpful - thanks!
 cmari


-- 
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] The $maketid and $setfield widgets

2014-06-03 Thread Danielo Rodríguez
Still a bit confusing to me how the parameter parameter is used. I think I 
will read the last documentation of your widgets 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 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] The $maketid and $setfield widgets

2014-06-03 Thread Matabele
Hi Danielo

Looks like I should write some documentation on how the title of the target 
tiddler is passed through the stack -- when I've worked it out myself I 
shall do so :-)

In general, the parameter to the received message is understood by the 
widgets to represent the title of the target tiddler -- the exception is 
the $maketid widget, which understands the parameter to the 
'tw-new-tiddler' message to represent the template (this, to maintain 
compatibility with the standard message.)

Unless the user overrides this default value for the parameter with the 
'param=' attribute, the same value will be passed on to the next widget in 
the stack -- this is the case even if the message is changed with the 
'message=' attribute.

I think I now have all of the widgets working correctly with this scheme.

regards

On Tuesday, June 3, 2014 9:51:15 PM UTC+2, Danielo Rodríguez wrote:

 Still a bit confusing to me how the parameter parameter is used. I think 
 I will read the last documentation of your widgets 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 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] The $maketid and $setfield widgets

2014-06-03 Thread cmari
Thanks for that explanation - very helpful!  Thanks also for the reminder 
about the find and replace possibility.  My solution evolved from one in 
which I had figured out how to use setfield to add a tag - so I had that 
piece already and was really focusing on shoehorning in tag removal.  Now 
that I've eliminated an entire $mangletags the whole thing is even more 
satisfyingly elegant
cmari

On Tuesday, June 3, 2014 12:14:13 PM UTC-7, Matabele wrote:

 Hi cmari

 I don't know what you are trying to achieve, but there's also a 'find and 
 replace' option for the $mangletags widget. Your code using two widgets 
 will add 'newtag' regardless of whether the tiddler was previously tagged 
 with 'oldtag' -- with the find and replace option, 'newtag' will be added 
 only to those tiddlers that were previously tagged 'oldtag'.

 The syntax in this case: $mangletags find=oldtag add=newtag 

 The widgets may be used in any order -- however, the default behaviour in 
 most cases is to pass on the received message to the next widget in the 
 stack. it is easier, therefore, to stack widgets of the same type adjacent 
 to one another -- changing the message only when the widget type changes 
 (as you have done.) The $maketid widget is the exception, as the 
 parameter caught by the widget becomes the default for the template 
 (maintaining compatibility with the standard 'tw-new-tiddler' message) -- 
 and the generated parameter is set to the value of the 'title' attribute. 
 All of the other widgets pass on the title of the target tiddler as the 
 parameter to the message by default (unless changed with 'param='), and 
 pass on the same message by default (unless changed with 'message='.)

 Hope this better explains how to use the widgets.

 regards

 On Tuesday, June 3, 2014 7:33:28 PM UTC+2, cmari wrote:

 Knowing that it was possible gave me the fortitude to continue with my 
 trial-and-error flailing!
 I still don't quite understand the pattern for which macro to use first 
 and when to add which message where, but in case it's helpful for someone 
 else, here's my working solution to accomplish the following with a single 
 button:
 1. set a field
 2. set another field
 3. add one tag
 4. remove another

 $setfield set=!!field1 setTo=value1
 $setfield set=!!field2 setTo=value2
 $mangletags find=oldtag message=tw-set-field
 $mangletags add=newtag
 $button message=tw-mangle-tagsbutton text here/$button
 /$mangletags/$mangletags/$setfield/$setfield

 (I haven't included a target because I put this in a tiddler called 
 MyButton and then use it inside other tiddlers, e.g., {{!!title||MyButton}} 
 )

 This is really helpful - thanks!
 cmari



-- 
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] The $maketid and $setfield widgets

2014-05-31 Thread Alberto Molina
Hi Matabele,

Thanks a lot for the widgets! I find them extremely useful to create 
newHere buttons and I'm presently trying to customize them.

When a new tiddler is created with your widgets, it is opened in view mode. 
How to get it in edit mode, like the regular new tiddler button ?

Regards,
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] The $maketid and $setfield widgets

2014-05-31 Thread Matabele
Hi Molina

There's an 'edit=' attribute available -- in the absence of this attribute, 
the default setting (edit=yes) should open the tiddler for editing. With 
edit=show' -- the widget should navigate to the new tiddler without 
opening, and with edit=no -- the new tiddler should be created in the 
background (all navigation suppressed.)

I have just tested again in a standalone v5.0.12-beta, and the behaviour is 
as expected -- if you are getting some other behaviour, please let me know 
with details of TW version, browser etc.

Whilst testing, I noticed that although the new tiddler appears in the 
search results, it fails to appear in the 'Recent' tab -- this was not the 
case when I was developing the widget with v5.0.10 on node.js :-(

regards

On Saturday, May 31, 2014 2:50:57 PM UTC+2, Alberto Molina wrote:

 Hi Matabele,

 Thanks a lot for the widgets! I find them extremely useful to create 
 newHere buttons and I'm presently trying to customize them.

 When a new tiddler is created with your widgets, it is opened in view 
 mode. How to get it in edit mode, like the regular new tiddler button ?

 Regards,
 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] The $maketid and $setfield widgets

2014-05-31 Thread Alberto Molina
Works fine. Thanks!

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] The $maketid and $setfield widgets

2014-05-31 Thread Matabele
Hi
 


 Whilst testing, I noticed that although the new tiddler appears in the 
 search results, it fails to appear in the 'Recent' tab -- this was not the 
 case when I was developing the widget with v5.0.10 on node.js :-(


With additional testing, I can confirm that a misbehaviour has arisen with 
the change from v5.0.10 to v5.0.12. After updating to v5.0.12, the title of 
the new tiddler appears in the 'Open' tab and in search results, but is 
absent from the 'Recent' tab (in v5.0.10, all was well.)

Does anyone know what has changed in v5.0.12 to cause this, and what remedy 
is necessary? The code of the navigator widget appears unchanged and I have 
failed to locate the change causing the misbehaviour.

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] The $maketid and $setfield widgets

2014-05-29 Thread BJ
HI Matabele,
maybe you do not need to regenerate the  tw-set-field event, ie your code 

this.sendMessage = tw-set-field;
if(this.catchMessage) {
   this.sendMessage = this.catchMessage;
}
this.dispatchEvent({type: this.sendMessage,param: this.sendParam});


can be replace with 

return true;

The at present you do not return anything from your handleFieldSet 
function, which is the same as returning null (which is the same as false 
in this case), this stops the event from propagating to the parent widget. 
- returning true will allow propagation (and so you do not need to call 
dispatchEvent()).

all the best

BJ
 
 On Tuesday, May 27, 2014 8:32:05 PM UTC+1, Matabele wrote:

 Hi Danielo

 Thanks, that would be appreciated -- it would be much cleaner to stack 
 successive $setfield widgets without having to intersperse $fieldset 
 widgets.

 regards

 On Tuesday, May 27, 2014 7:26:48 PM UTC+2, Danielo Rodríguez wrote:

 I have to digg into your code, but maybe you are not stopping the event 
 propagation. If so your widget will get the same message twice. I'm not 
 sure about this and I don't remember exactly how this works. I studied it a 
 while ago and I think that I understood it then. Just let me check. 



-- 
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] The $maketid and $setfield widgets

2014-05-29 Thread Matabele
Hi BJ

Many thanks - precisely the answer I was looking for -- I will modify the 
plugin accordingly and publish when I have done some testing. 

Does this work reliably with all browsers?

regards

On Thursday, May 29, 2014 9:27:16 AM UTC+2, BJ wrote:

 HI Matabele,
 maybe you do not need to regenerate the  tw-set-field event, ie your code 

 this.sendMessage = tw-set-field;
 if(this.catchMessage) {
this.sendMessage = this.catchMessage;
 }
   this.dispatchEvent({type: this.sendMessage,param: this.sendParam});


 can be replace with 

 return true;

 The at present you do not return anything from your handleFieldSet 
 function, which is the same as returning null (which is the same as false 
 in this case), this stops the event from propagating to the parent widget. 
 - returning true will allow propagation (and so you do not need to call 
 dispatchEvent()).

 all the best

 BJ
  
  On Tuesday, May 27, 2014 8:32:05 PM UTC+1, Matabele wrote:

 Hi Danielo

 Thanks, that would be appreciated -- it would be much cleaner to stack 
 successive $setfield widgets without having to intersperse $fieldset 
 widgets.

 regards

 On Tuesday, May 27, 2014 7:26:48 PM UTC+2, Danielo Rodríguez wrote:

 I have to digg into your code, but maybe you are not stopping the event 
 propagation. If so your widget will get the same message twice. I'm not 
 sure about this and I don't remember exactly how this works. I studied it a 
 while ago and I think that I understood it then. Just let me check. 



-- 
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] The $maketid and $setfield widgets

2014-05-29 Thread Matabele
Hi BJ

Appears to work fine. I have updated the $setfield widget and uploaded 
the new version and updated documentation to: http://wills.tiddlyspot.com/

This update retires the need for the fieldset widget, as multiple 
$setfield widgets can now be placed one after the other in the stack. As 
a consequence, I have removed the fieldset widget from the plugin.

Many thanks for your assistance.

regards

On Thursday, May 29, 2014 9:27:16 AM UTC+2, BJ wrote:

 HI Matabele,
 maybe you do not need to regenerate the  tw-set-field event, ie your code 

 this.sendMessage = tw-set-field;
 if(this.catchMessage) {
this.sendMessage = this.catchMessage;
 }
   this.dispatchEvent({type: this.sendMessage,param: this.sendParam});


 can be replace with 

 return true;

 The at present you do not return anything from your handleFieldSet 
 function, which is the same as returning null (which is the same as false 
 in this case), this stops the event from propagating to the parent widget. 
 - returning true will allow propagation (and so you do not need to call 
 dispatchEvent()).

 all the best

 BJ
  
  On Tuesday, May 27, 2014 8:32:05 PM UTC+1, Matabele wrote:

 Hi Danielo

 Thanks, that would be appreciated -- it would be much cleaner to stack 
 successive $setfield widgets without having to intersperse $fieldset 
 widgets.

 regards

 On Tuesday, May 27, 2014 7:26:48 PM UTC+2, Danielo Rodríguez wrote:

 I have to digg into your code, but maybe you are not stopping the event 
 propagation. If so your widget will get the same message twice. I'm not 
 sure about this and I don't remember exactly how this works. I studied it a 
 while ago and I think that I understood it then. Just let me check. 



-- 
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] The $maketid and $setfield widgets

2014-05-28 Thread Felix Küppers
Hi Matabele,

just want to say thanks! Your plugin solved my problem that I had with the 
$newtiddler widget, where I had to predefine placeholders for fields in 
order to set them.
Now I have all the flexibility I need, by being able to set 
placeholders/tags/fields.

so thank you once more for your work ;)



On Tuesday, May 27, 2014 10:01:10 AM UTC+2, Matabele wrote:

 Hi 

 I have been working on a couple of widget plugins which address problems I 
 was having when developing TW5 applications -- they may be found here: 
 http://gwiz.tiddlyspot.com

 The $setfield widget was my response to the need to initiate more than 
 one function with one button. Starting out with a mechanism borrowed from 
 the linkcatcher widget, I developed a pair of complementary widgets that 
 could be assembled in a stack around a button widget -- the title of the 
 target widget being passed through the stack with an event parameter.

 The $maketid widget was my response to the spurious javascript errors I 
 was experiencing with the $newtiddler widget. My efforts to address the 
 error by modifying the $newtiddler widget failed, and I resorted to 
 rewriting the widget by adopting the mechanism borrowed from the 
 linkcatcher widget. This appears to have cured the bad behaviour of the 
 $newtiddler widget, at least in the context in which I was experiencing 
 problems.

 I have constructed the widgets in such a way that they may be used 
 together in the same stack. Other widgets could be developed using the same 
 mechanism which could then be added to the widget stack (the 
 $fieldmangler and $linkcatcher widgets are partially compatible.)

 I would welcome any feedback with respect the concept of the widgets, and 
 any ideas with respect modifying the code to broaden the context of their 
 application.

 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] The $maketid and $setfield widgets

2014-05-27 Thread Matabele
Hi Danielo

Don't know the technicalities, but when I try this, I get stack overflow 
errors (and 'field-two' doesn't get set):

$setfield set=!!field-two setTo=two
$setfield set=!!field-one setTo=one message=tw-set-field
$button message=tw-set-field param=TargetSet/$button
/$setfield
/$setfield

Likely my deficient knowledge of javascript -- perhaps there's a way to fix 
this?

regards

On Tuesday, May 27, 2014 3:48:44 PM UTC+2, Danielo Rodríguez wrote:

 Hello Matabelle 

 I succeed editing the newtiddler widget to add the hability of define 
 tags, but I like a lot your idea of chaining widgets. Could you explain 
 this limitation? I don't understand why :

 Unfortunately, $setfield widgets can not be stacked in this way, as the 
 same message can not be sent from a widget as the message caught by the 
 widget. A transposed $fieldset widget is, therefore,

 There are several widgets that does not suffer from this limitation. The 
 link catcher widget does exactly this, chaining messages. 



-- 
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] The $maketid and $setfield widgets

2014-05-27 Thread Danielo Rodríguez
I have to digg into your code, but maybe you are not stopping the event 
propagation. If so your widget will get the same message twice. I'm not sure 
about this and I don't remember exactly how this works. I studied it a while 
ago and I think that I understood it then. Just let me check. 

-- 
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] The $maketid and $setfield widgets

2014-05-27 Thread Matabele
Hi Danielo

Thanks, that would be appreciated -- it would be much cleaner to stack 
successive $setfield widgets without having to intersperse $fieldset 
widgets.

regards

On Tuesday, May 27, 2014 7:26:48 PM UTC+2, Danielo Rodríguez wrote:

 I have to digg into your code, but maybe you are not stopping the event 
 propagation. If so your widget will get the same message twice. I'm not 
 sure about this and I don't remember exactly how this works. I studied it a 
 while ago and I think that I understood it then. Just let me check. 

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