--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/Q5zMj0hL4Jk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/f87f793e-13c4-4781-a912-b1aeacb3fe29%40googlegroups.com.
Yeah, same here
On Tue, 5 May 2020, 03:03 'Mark S.' via TiddlyWiki, <tiddl...@googlegroups.com> wrote:
--I don't get an error message, but the checkbox never binds to the field, and you can never flip the field away from "open".The same thing happens if you use "tags".
On Monday, May 4, 2020 at 2:14:21 PM UTC-7, Riz wrote:Just checking if I am the only one with this errorSteps to reproduceDownload an empty tiddlywikiCreate a new tiddlerPaste the following<$checkbox field="list" checked="open" unchecked="closed" default="closed"> Is it open?</$checkbox>SincerelyRiz
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/Q5zMj0hL4Jk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddl...@googlegroups.com.
With all due respect this is not a bug its a footnote.
If you must make use of core fields use them as designed.
Not withstanding my above comments I always thought it was sad that the core used such valuable field names such as type and list when they could have had a prefix e.g. tw-list but that's evolutionary design for you, we sometimes take hostages of our own future.
Somewhat in jest
Tony