Thanks Mark,
I am trying to use this now. I have duitfuly tagged it $:/tags/Macro saved
and reloaded
in Both the key tiddler and below placed
<> used other field names and ways of referencing the
field name yet nothing apears.
I have looked around but can not see why this would not work,
There is a compatibility table for this feature here
http://caniuse.com/#feat=input-number (notes for iOS Safari - 'UI widget
does not include increment/decrement buttons'. 'UI widget does not take the
"step", "min" or "max" attributes into account.')
On Monday, May 15, 2017 at 4:31:14 AM
Hi Tony,
I really hope we can use your experiences as a further spur to improving
the documentation for Tiddlywiki. It's something the community have been
aware of a long time and which we have (imo) yet to seriously address. Some
measure of the difficulty we experience in this regard is in
Here's an improved (?) version that uses the existing field value as a
default:
\define editnsave(field)
<$vars tid="$:/temp/$(currentTiddler)$" fld=
"$:/temp/$(currentTiddler)$!!$field$" fldx=
"{{$:/temp/$(currentTiddler)$!!$field$}}" >
$field$: <$edit-text tiddler=<> field="$field$"
Thank you a lot, from Japan!
It's a must for Kanji(Chinese) character!
Example→例
How to→方法
2017年5月14日日曜日 12時50分07秒 UTC+9 Birthe C:
>
> Tiddler $:/config/Search/MinLength is default set to 3.
>
>
>
> Birthe
>
>
> Den søndag den 14. maj 2017 kl. 05.32.44 UTC+2 skrev chaonuo:
>>
>> hi,
>>
>> I rely
Mark,
I am yet to test this but could it be extended as follows
<>
But idealy
<>
to prepopulate it?
It is often helpful to utilise the edit of a value to display it as well so
that you can save screen realestate.
Regards
Tony
On Thursday, August 10, 2017 at 1:12:47 AM UTC+10, Mark S.
Arlen
Please detail your usage of the set widget that would help because I ghave
not yet being able to set a relaible psudo constant as what passes through
is subseqently evaluated.
Thanks
Tony
On Wednesday, August 9, 2017 at 10:02:02 PM UTC+10, Arlen Beiler wrote:
>
> And, since no one
Richard,
Thanks for your empathy.
The best example of the first case Psudo constants is in the post above,
this works for me in subtiddlers however as it returns the constant only in
the form <> it is still of limited value. Lets imagin I have
a value it may even be the tiddler name I have
Thanks all for your comments,
I will investigate the possibilities here, However my key point is it
should be fairly trivial to find a clear solution coded in the the core and
documented thoroughly in the documentation.
My Key point is these basic needs are not addressed in the current
Hi Arlen,
If the sky is the limit:
It would be great to have a service which would make it possible to
transform TWs into mobile apps and deploy them in the appstores.
Talking monetarisation I could imagine free apps which are paid in
advance and some way to share the gain on apps which are
Considering that you've just bumped a 3 year old thread, I wouldn't hold my
breath.
The TOC macro will use the caption field by default, and you can have more
than one tiddler with the same caption. Maybe that will give you better
results?
Good luck,
Mark
On Wednesday, August 9, 2017 at
Re request #2, use the following macro. Put it in a tiddler tagged
$:/tags/Macro.
Then put <> anywhere in the tiddler that you want to
edit the field. This will create an edit field and a reset button. Use the
* button the first time you use the field to synch it with the current
values. Edit
I still think anchor tags that can be used to generate a toc within a
tiddler could be useful. One example where I would like to use them is in
code documentation. If you generate a document for each module, you may
want a section with a heading Change Log. From my experience, you can't
create
Thanks Eric! I was missing the 'a' in hsla when I tried it. I prefer this
way to rgb(a)
On Wednesday, August 9, 2017 at 11:08:23 PM UTC+10, Eric Shulman wrote:
>
> On Wednesday, August 9, 2017 at 5:50:34 AM UTC-7, RichardWilliamSmith
> wrote:
>>
>> I'll answer my own question :) one way is to
On Wednesday, August 9, 2017 at 5:50:34 AM UTC-7, RichardWilliamSmith wrote:
>
> I'll answer my own question :) one way is to use 'rgba', like this
> - rgba(52,200,52,0.2) where the last value it the alpha. Should also be
> able to use 'hsl' but that doesn't seem to work (?)
>
The values for
You'll have to explain what you mean. The method I described doesn't lose
focus.
On Wednesday, August 9, 2017 at 12:28:42 AM UTC-7, Danielo Rodríguez wrote:
>
>
>
> El miércoles, 9 de agosto de 2017, 6:14:48 (UTC+2), Mark S. escribió:
>>
>> Adding to what Richard suggests, if you only want your
I'll answer my own question :) one way is to use 'rgba', like this
- rgba(52,200,52,0.2) where the last value it the alpha. Should also be
able to use 'hsl' but that doesn't seem to work (?)
On Wednesday, August 9, 2017 at 10:20:35 PM UTC+10, RichardWilliamSmith
wrote:
>
> Hi Mat,
>
> What
Hi Mat,
What would you put it if you wanted it only 50% transparent (~translucent).
It seems like 4/8 digit codes (with alpha channel in the last 1/2) are part
of the css 4 spec, but don't seem to be implemented right now (?)
Richard.
On Wednesday, August 9, 2017 at 9:44:55 PM UTC+10, Mat
And, since no one mentioned it yet, the set widget is probably what you're
looking for for pseudo constants. Documentation is on tiddlywiki.com.
On Aug 9, 2017 07:53, "RichardWilliamSmith"
wrote:
> Just to add that you can go to Tiddlywiki.com and create a new
Just to add that you can go to Tiddlywiki.com and create a new Tiddler with
the text <$edit-text field="text"/> and give it the tag
$:/tags/ViewTemplate you get a live edit field that doesn't lose focus. I
guess the difference between this and an edit-text widget as part of the
tiddler content
charleyc...@gmail.com wrote:
>
> Everything white being translucent. Or dark grey, in my case (custom
> palette).
Ok, then you can go to that custom palette and simply locate the color
fields that have that dark gray color code, and exchange the color code for
the word *transparent*. I think
The method I suggested works without losing focus when tested on
Tiddlywiki.com. I just tried transcluding the body element itself
($:/core/ui/EditTemplate/body) and that works too. I do remember there
being an issue with losing focus when updating the content of a tiddler, as
you describe,
Everything white being translucent. Or dark grey, in my case (custom palette).
--
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
Ciao Arlen
1 - Would payment be through Amazon? IF SO, that is very *good*. Its proven
resilient & pretty clear.
2 - Part of the problem you might face is that the current TYPE of user
(i.e. a lot of us in this group) are cheapskates--I can't see you making
money from people like us :-)
3 -
El miércoles, 9 de agosto de 2017, 6:14:48 (UTC+2), Mark S. escribió:
>
> Adding to what Richard suggests, if you only want your special fields to
> appear, you can make a tiddler with $:/tags/ViewTemplate and populate it
> with:
>
You are missing the point that you CAN NOT edit a field on
25 matches
Mail list logo