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
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
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
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
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,
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
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
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,
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
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
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
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:
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
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
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
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
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.
--
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
18 matches
Mail list logo
