Finally got it figured out with the following code:
<$button> remove extraneous text
<$list filter="[tag[Railroads]]" variable="tid" >
<$list filter="[get[text]split[\define]splitregexp[.*>]]"
variable="pap">
<$action-setfield $tiddler=<> text=<> />
On Friday, November 20, 2020 at 11:11:08
Alright, I've made a lot of progress. I would now like to be able to delete
all of the previous defines and transcludes that I had at the beginning of
the text field. I want to create a button that would do this automatically
for me. I know it's going to use splitregexp, but I am totally new to
I'm always terrible at giving enough information and I apologize. After
some thinking about it, I finally figured out a way to do it. I put the map
link in a field named maplink and then put {{!!maplink}} in the appropriate
area of the infobox table. Works like a charm. Whether you directly
Damon,
So as I understand it when you transclude Infobox it is rendered with the
current tiddler set to the tiddler in which your code snipit is written
unless you take other steps to alter the currentTiddler, this is supported
by the idea that you subsequently transclude the text field
You're right, I forgot to show my code which I now have below:
<$transclude tiddler="Infobox">
<$transclude field=text mode=block/>
I can't have a globally defined map link because each railroad has a unique
map.
I misspoke earlier. My infobox stylesheet is being used.
Damon
On Wednesday,
Buff,
If you place \defines in a tiddler tagged $:/tags/Macro it can be used by
name globally, similarly css placed in a tiddler tagged $:/tags/Stylesheet
will also be usable globally, this is the approach to use when you want to
reuse.
Remember when using theit assumes
tiddler=<>, what
I've also noticed that the styling I had with the infobox didn't get
applied.
Damon
On Wednesday, November 18, 2020 at 4:15:33 PM UTC-7 History Buff wrote:
> Tones,
>
> The aside element worked as long as it was above the transcluded body. The
> table didn't really work the way I wanted
Tones,
The aside element worked as long as it was above the transcluded body. The
table didn't really work the way I wanted becuase, if the body text was
very long, it wouldn't wrap around the infobox.
Now the only issue I have remaining is the map within the infobox. The link
to the map is
Tones,
That got me a step closer with what you suggested. The aside element was
able to keep the infobox from overlapping the footer, but the body text and
infobox were still stacked. The table worked best but didn't allow the body
text to wrap around the infobox if the text was much longer
Ahhh,
Yes, you need to find a way to have the text you require inside the
tiddler, as in your image, it is inside the tiddler.
- You can hide the default body with a field hide-body=yes on a give
tiddler,
- Then you introduce a replacement to display "the body" <$transclude
Hey Tones,
Yes, I did try changing the order using the tag pill. That's how I moved it
from above the body text to below. There was no order that would put it in
the position that I wanted. It seems that each ViewTemplate takes up its
own horizontal space within the tiddler and that space
Damon,
Have you tried changing the order of the items tagged $:/tags/ViewTemplate
using the tag pill?
<>
Once you resolve it you can use the list-before or list-after fields to set
the order in place
eg
list-before $:/core/ui/ViewTemplate/body
Regards
Tones
On Wednesday, 18 November 2020 at
12 matches
Mail list logo
