Forum

Manually changing values

#1

I have another problem that I haven’t found a solution for yet.

The thing is, I have created a loop for changing positions of objects on screen with the mouse. So far so good, but sometimes it would be nice to be able to type a value straight into the textnode, instead of dragging with the mouse. But I can’t change the text node, since it’s input node is connected.

Is there a workaround to be able to do these kind of things without disconcting nodes? Can it be done using R and S nodes for example?

#2

since it’s input node is connected.

what exactly do you mean with “text node”?

is it an IOBox (Value Advanced) visualizing your mouse values?
seems so.

so i assume you need both

  • the mouse input
    +and
  • some other input.

this means you need kind of a gateway/switch/whatever.

what behaviour do you expect from this gateway?

maybe LTP (Spreads).v4p ( see kalle.Modules.Spreads ) can help you?

#3

or is it the recursive way using FrameDifference (Animation) and FrameDelay (Animation) ?

#4

or is it the recursive way using FrameDifference (Animation) and FrameDelay (Animation) ?

ft.v4p (24.2 kB)

#5

That’s great, thanks.

But this way you can manually adjust the ‘relative’ displacement, but not the ‘absolute’ position that is reflected in the TranslateX and Y IOBoxes at the bottom. That would be the values that I would like to be able to control using the mouse AND directly.

Why? Think of an ordinary program with a slider controlling some parameter. A textbox reflects the chosen value, but you can also just click the textbox an fill in the value you want. The slider will also jump to the new position at that time. It is such a common way of using software… (EDIT: this can be done using an IOBox with a slider, but I want to be able to have that kind of control through other means like mouse, keyboard, midi, and still edit manually…)

#6

here i like to point out, that the IOBoxes in vvvv are somehow part of the code, they represent the value itself and are not meant to form a GUI for your application. if you like to have sliders or buttons to control you application, you should implement them in the renderer window. there are many modules and plugins to do that.

have a look at this page: Custom GUI Method Collection

#7

I managed to do it, allthough it is very slow at this time (maybe I should check if something changes and only setPatch if the input has changed), so only intended for configuring settings and saving the patch with your preconfigured values.

The example uses a simple toggle button, but it would be more useful with real values of course.

I would be happy to use it in a renderer, but has anyone already implemented TEXTBOXES in a renderer, where you can type your desired value? I have to get a few things working and don’t have the time to develop that myself. If you know of such a thing, please let me know, for I haven’t found it.

…are not meant to form a GUI…

But everyone uses sliders, toggle buttons and bangs for controlling stuff, at least in examples, so maybe they are not strictly meant for this, but they are the only standard way for IO. And they happen to be called IOBoxes, which suggests that the developers did have Input/Output in mind when they were developing them.

Besides, I wanted text input, next to other input methods like mouse, midi, etc.

#8

I managed to do it, allthough it is very slow at this time (maybe I should check if something changes and only setPatch if the input has changed), so only intended for configuring settings and saving the patch with your preconfigured values.

The example uses a simple toggle button, but it would be more useful with real values of course.

I would be happy to use it in a renderer, but has anyone already implemented TEXTBOXES in a renderer, where you can type your desired value? I have to get a few things working and don’t have the time to develop that myself. If you know of such a thing, please let me know, for I haven’t found it.

…are not meant to form a GUI…

But everyone uses sliders, toggle buttons and bangs for controlling stuff, at least in examples, so maybe they are not strictly meant for this, but they are the only standard way for IO. And they happen to be called IOBoxes, which suggests that the developers did have Input/Output in mind when they were developing them.

Besides, I wanted text input, next to other input methods like mouse, midi, etc.

IOBox Loopback.zip (4.6 kB)