📝 ❓ How to widen tiddlers (aka storyriver) with the mouse?

[Cd.K]

Is there a plugin? 

[Mat]

Other than some dabblnig by me a few years ago I don't think there's a ready plugin - but it should not be overly difficult if you accept the widening to be made with a rangewidget (as opposed to e.g "grabbing" the storyriver itself).

<:-)

[Mark S.]

The range widget was such a neat idea, I thought I would investigate. Unfortunately, the target field requires a "px" designator. Also

there are 3 fields that need to be modified at once if you don't want a mess on screen, but the "actions" clause doesn't seem to work with the range widget. So a

button is needed. This is what I came up with ...

Set your system to fixed story river, fluid sidebar. Make a tiddler and tag it with $:/tags/Sidebar. With contents:

\define myactions()
<$action-setfield $tiddler="$:/themes/tiddlywiki/vanilla/metrics/storywidth" $field="text" $value={{{ [[$:/themes/tiddlywiki/vanilla/metrics/storywidth2]get[text]addsuffix[px]] }}} />
<$action-setfield $tiddler="$:/themes/tiddlywiki/vanilla/metrics/storyright" $field="text" $value={{{ [[$:/themes/tiddlywiki/vanilla/metrics/storywidth2]get[text]addsuffix[px]] }}} />
<$action-setfield $tiddler="$:/themes/tiddlywiki/vanilla/metrics/tiddlerwidth" $field="text" $value={{{ [[$:/themes/tiddlywiki/vanilla/metrics/storywidth2]get[text]subtract[86]addsuffix[px]] }}} />
\end
<$range tiddler="$:/themes/tiddlywiki/vanilla/metrics/storywidth2" min="600" max="1000" default={{{ [[$:/themes/tiddlywiki/vanilla/metrics/storywidth]removesuffix[px]] }}} increment="1" actions=<<myactions>>/>

<$button actions=<<myactions>>>Set</$button>
{{$:/themes/tiddlywiki/vanilla/metrics/storywidth2}}

Now you can use the range widget to set the width, and then click on "set" to activate the changes.

[Mohammad]

Mark,

 How about fixed sidebar fluid story river, isn't it to just set the

$:/themes/tiddlywiki/vanilla/metrics/sidebarwidth

--Mohammad

[PMario]

Hi,

If you have a look at this video https://youtu.be/7Zvff75DwWM?list=PLuiC_HFhI4OzcqS8wBPSgT3nEK8WAXswk&t=25 you can see, how to adjust it. You only need to watch 20 seconds

-m

[@TiddlyTweeter]

Ciao Mark S.

I tested that out on Edge. Very neat starting point. Works very well for px range. But IF only ...

Best wishes

TT

[Mat]

OK, since Mark decided to push forward. Here's my dabbling from a few years back:

In TWaddle, go to Ctrlpanel > Appearence > Size Settings  or directly to the tiddler you see there, here.

Once that tiddler is active you see a slew of range based settings. The thing is, this was created before the range widget was implemented in TW and some other things have since been updated in TW as well.

Mark S. wrote:

Unfortunately, the target field requires a "px" designator.

Support /come with input to this issue: https://github.com/Jermolene/TiddlyWiki5/issues/3252

Also, if I recall, the new math ops are made to disregard non-digit suffixes such as 670px. Maybe that is useful in this context.

<:-)

[Mark S.]

I'm not sure what the "if only" is about. You want a different appearance? I'm sure the CSS wizards here could

cook that up in no time. Note that the slider actually changes 3 settings at once. If it didn't, the result would

quickly become unreadable.

The next step would be to make another slider for sizing fonts. They also need to be changed in step

(the line height and font size).

Note that google flags "googlegroups" as a deceptive site. I suppose because it's pretending to be google.

Thanks!

Mark

[Mark S.]

When I tried to change the font settings, suddenly the entire slider became unusable.

I think the trick is to change two settings in parallel. So that way the font won't become too big

or small for the line size.

The same for changing the width -- 3 different settings need to change in lock step. That's what I did

in the quick range widget example.  This works within a given range of settings. I

With the px, I just manipulated the number and then appended the "px". I looked at the

thread, but it appears nothing has happened since 2018. So I suspect it's a temporal orphan.

If the "actions" attribute was added to the widget, then it might not need any other fix.

Thanks!

[@TiddlyTweeter]

IF only, sorry I was obscure. I meant that PX is a problem. It is NOT your direct issue.