Wrote

It is useful when you use one slider to fine tune several independent values (by switching between them)

.

Alex,

I don't understand "completely" your tune several independent values.
I suppose you mean adjusting "parameters" wrt model/modeling.
That was my comment reply to Sergio/Davide. Keep reading "Samples"
that's where you will find model functions already done. The last
two typical: Alcotest, Water viscosity. Modeling is a life time
addiction, no cure for that except the day I will suck the roots,
no urgency for that day ! can't even backward the clocking slider/timer.

Cheers, Jean

Wrote

I can do it, but this means that the slider will be used just as visual feedback, since any user change triggers the evaluation that restore the input value.

Wrote

Wrote

It is useful when you use one slider to fine tune several independent values (by switching between them)

.

Alex,

I don't understand "completely" your tune several independent values.
I suppose you mean adjusting "parameters" wrt model/modeling.

Davide and Jean,

This is how a predefined initial slider value would have been used for me before and can be used by someone in future:



-> fine tune the value using the slider
-> the value to a global variable which is passed back to the block of calcs

What I did before:

Have two sliders that define XY coordinates of the point. Use only those two sliders to modify coordinates of about 15 points. This would have been possible if the slider value could be preset from the workbook:
-> select a point
-> slider is positioned at the current point's coordinate
-> adjust the slider
-> point coordinate is stored in a global variable and becomes the new default position of the slider
-> select different point
-> repeat

To be fair I have abandoned the XY coordinate definition method in favor of using modeler region for that purpose. However the example demonstrates that presetting the initial slider position can be useful in certain cases.

Thanks Alex,

I understand why the slider is useful for you: set the coordinates of a drawing shape.
Not like me: tuning parameters of a model function [conjointly OriginLab, Smath Genfit]

Cheers, Jean.

Eastern Canada, still very fresh temperature.

... forgot one of the most pertinant use of the slider:
slide the convolving function [sliding integration].
One of so many RemToDo.

PLUGIN UPDATED SMath Studio 0.98.5952 Nightly Build only

• SMath Viewer: the same slider of the canvas will be used, instead of the standard .NET Trackbar; this makes the project more consistent and solves several bugs even in the worksheet; moreover allows to remove the scale factor;
  
• Scale factor removed; decimal values are now a valid input.
  ** if you don't have settings from canvas, transition is fully driven by the region;
  ** if you have settings from canvas and scale factor != 1, you have to update the input values from the canvas and change the name of the variable that contains the input settings or save and reopen the worksheet (an error message will be shown inside the region, output value will be undefined until you fix the settings);
  
• Added new key for settings from canvas: "value" (if you want to disable input from users, region will be used just as a visual feedback);
  
• Added new key for settings from canvas: "initial value" (the value of the region will be set as this value if it changes);

Slider Region.sm (28 KiB) downloaded 155 time(s).



P.S. If everything works fine, I'll relase a stable version for SS from 0.97.5346 to latest

When I show the description of the slider, I receive an exception when trying to open the settings.

Picture and Exception text attached. I'm using SMath 0.98 (build: 6077) and plugin version (0.4.6078.4892).


exception.txt (25 KiB) downloaded 113 time(s).

Fixed & updated, thank you!

A quick question, are there tags to enable checkboxed options?



Regards

Wrote

A quick question, are there tags to enable checkboxed options?



Regards

The first should enable a permanent box containing the current value right under the slider track, it does not affect the field on the right.

The second should enable the drop down list on the right (if there is the relative canvas setting set, it should be freezed, by design)

What I meant is if there are tags which can enable them like other tags.



for example;

"tickValueShow" = 1 --"true"
"initialValueShow" = 0 --"false"

Regards

Wrote

What I meant is if there are tags which can enable them like other tags.



for example;

"tickValueShow" = 1 --"true"
"initialValueShow" = 0 --"false"

Regards

Ah, got it!

Nope, ticksshow is driven by tickPosition=none for off or another value for on. (I might add it, though)

The value box should have its own option for sure but IDK why is only partially implemented (I don't remember if there were issues or it was lost and forgot in some more urgent update. I'll give it a closer look)

PLUGIN UPDATED SMath Studio 0.99.7822 and later

• settings from canvas: added options to show "value label";
  
• settings from canvas: added options to show "tick labels";
  
• Settings from canvas: extended valid keywords separators
  
• Settings from canvas: canvas variable now doesn't have anymore to contain only valid settings
  
• Documentation updated

Thanks, Davide, for updating the beloved Slider Region!

I'd like to make a few suggestions for further improvements:

1) The possibility to have a region with multiple slider inputs, so the output is a vector instead of a number;

2) The creation of a region that bundles together some of the existing controls. For instance: first column is a slider, second column is a comboboxlist, so the output is a vector/matrix.

3) If (1) is implemented, making the setting that controls the number of inputs a variable. In other words, making it dynamic.

These functions would considerably facilitate the input of data in the program.

In the example below, for each depth value, I need different variables and later group than with another function. Not even mentioning the work in formatting the whole thing and the grotesque text beside:



To emphasize the issue, I point it out that I can't set the value to a vector's position, like below:



So yeah, I'm stuck to lots and lots of variables, as far as I know.

Hope I'm making sense and you consider some of these ideas. Thank you for the great work!

Hi, Davide! Sorry to bother, but could you give me a reply on the above?

Hello and sorry for the late answer.

The problem to multiply regions in the same container is how to implement and manage the multiple input/output values (variables, canvas settings, mouse/keyboard actions, serialization, viewer compatibility, etc...) and it might be even harder to manage "conditional inputs“ based on output values of other controls in the same group.

Probably a new datagrid region (a table with controls of each type repeated in same columns or rows) would be the most reasonable way to cover all the points using the existing code, but still require a lot of work, and existing regions have to be refactored f.e. to accommodate a flexible layout.

I already plan to implement tables in WriterRegion so I'll keep this in mind to reuse the code.

As for now in cases like the one in your screenshot I suggest to use a stack/augment approach with fixed output names, and simply copy paste as many times as needed (maybe reserving a whole page for this purpose)., something like the following pseudocode.

initialization:
regions to copy/paste:
then you can use the "M" output

Thank you, Davide!

I'll think about it... The mouse wheel should be the default way for the fine tuning of the slider, but I understand some wheels are not good.