Saq,
I do think I complicated my initial post. The issue was "having and editing
multiline text in custom fields", and sill is but as you say I went onto
"using the framed editor with fields other than text".
You have answered my question in so far as saying it was not just Wiki text
macros or widgets that stops the framed editor behaving as I wish.
Perhaps I need to reconsider my approach here.
Thanks
Tony
On Thursday, June 11, 2020 at 10:53:33 PM UTC+10, Saq Imtiaz wrote:
>
> @Tony your initial post made it seem like the issue was having and editing
> multiline text in custom fields. It seems however that your issue is using
> the framed editor with fields other than text for multiline content.
>
> AFAIK the framed editor will default to using an input element, regardless
> of the tag specified, for fields other than text unless the field has a
> definition in fieldModules with an edit tag specified.
>
> Off the top of my head and completely untested, this is would look
> something like:
>
> $tw.modules.define("$:/boot/tiddlerfields/mycustomfield","tiddlerfield",{
> name: "mycustomfield",
> editTag: "textarea"
> });
>
> On Thursday, June 11, 2020 at 2:24:03 PM UTC+2, TW Tones wrote:
>>
>> Folks
>>
>> Thanks for your advice but I am aware of your tips. The problem is
>> getting the edit body template to operate on an additional text field, it
>> is but it refuses to permit multiple lines.
>>
>> This method would permit use of the tool bar as in saqs streams and other
>> implementations that operate on text fields. In the modified versions I
>> attached I can't identify where I can change the behavior.
>>
>> Thanks for any other ideas.
>>
>> Tony
>>
>>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/754ed1c8-25e6-4cf4-9718-daa59a017628o%40googlegroups.com.
