Ventuz Forum

florian wrote:You could use the command lines options

Code: Select all

VentuzPresenter.exe -kill

l

That will kill running Ventuz instances when starting a new one - but not just kill the running one and return to the desktop.

cheers,
rou

Alt-F4 works perfectly fine!

But... You can also use VMS to kill Ventuz. That's what the Config Editor does. That way you can put an exit button into your presentation

I've built such a kill button once. It even has a safety so it won't kill your designer

cheers,
rou

we're a bit busy, so the final release has to wait a bit, but check out this new preview with great music made by Gösta Bergfeld!

cheers,
rou

Yeah, I agree that's probably the best workaround atm ;) However one thing I like about Ventuz is that it does not have invisible connections. I've seen quite a few applications that have exactly that problem: you don't see connections. Some nodes are connected by putting in another node's name in t...

Yes, that would be a workaround. However I don't want to use a network protocol for such a basic functionality.

thanks,
rou

Thought for a moment I had a workaround. Using an event in the scene data. So inside the interface container I would bind an outgoing event to trigger the scene event. Then outside the container I would get my event not directly from an output of the interface container, but from the scene event. Th...

Hi, this is not a big one... but it cost me a moment to figure out what's going on, so I'll annoy the forum in return. Create a new empty scene Create a touch translation node, followed by a rectangle. Set the touch limits: active: true MinX = 0 MaxX = 0 MinY = 0 MaxY = 10 Move the rectangle up a bi...

here's an example. Try throwing the rectangle around in both modes.

cheers,
rou

Hi, I am working in a pixel space. I created an ortho projection with the screen dimensions. Elements are scaled using pixels - so a button could have something like 200px. I am using a lot of touches. So far no problem. Now I want to use the touch transform's inertia behaviour - and I can't really....

Hi, When you copy a node, you can keep its bindings. That's a very good help! But it only works for inputs. I know, this would not work for all outputs, since they often have a 1:1 binding (for instance output float to float expression). But it would be awesome to see this feature for those outputs ...