djdutschi
I need a Mapping Command to close the Poi Editor Window.
Greatings Dani
Greatings Dani
Posté Sun 14 Jun 15 @ 11:26 am
PachN
You could use ALT+F4
Posté Thu 18 Jun 15 @ 7:53 am
djdutschi
Ok this works .
But it is not possible to make an own mapping command for this function?
Ich kann den Poi ja auch über den Controller öffnen.
Dann wäre es schön dieses Fenster damit auch schliessen zu können.
Greatz Dani
But it is not possible to make an own mapping command for this function?
Ich kann den Poi ja auch über den Controller öffnen.
Dann wäre es schön dieses Fenster damit auch schliessen zu können.
Greatz Dani
Posté Thu 18 Jun 15 @ 2:29 pm
djdutschi
Ok now I become a New Update.
Now I can this Close with ESC .
My Question is , why I can't mapping a own Button to Oper and Close the BPM & Poi Editor Windows?
Now I can this Close with ESC .
My Question is , why I can't mapping a own Button to Oper and Close the BPM & Poi Editor Windows?
Posté Fri 19 Jun 15 @ 6:10 am
PhantomDeejay
What I don't really understand is this:
If you open any of the editors you need to use your mouse to do the tasks you want. Therefore, I can't see any benefit opening/closing the editors through a controller...
Can you please explain me how it would be useful to open/close via controller ?
If you open any of the editors you need to use your mouse to do the tasks you want. Therefore, I can't see any benefit opening/closing the editors through a controller...
Can you please explain me how it would be useful to open/close via controller ?
Posté Fri 19 Jun 15 @ 6:21 am
djdutschi
Whether it makes sense that must decide each themselves.
I can definitely control much of the POI editor with my controller.
For example with the Stripsearch and jog wheel and Hotcue buttons.
So it's a great deal that could be operated without mouse ;-)
I can definitely control much of the POI editor with my controller.
For example with the Stripsearch and jog wheel and Hotcue buttons.
So it's a great deal that could be operated without mouse ;-)
Posté Fri 19 Jun 15 @ 7:03 am
PhantomDeejay
I'm asking in order to understand. Don't take me wrong.
As with ANY new feature we add on the software, it must have a point that we believe it will benefit the users and their workflow. Also we don't want to clutter VDJScript with millions of commands for any possible "action" a user might want to do.
So, back to the subject: Why would you open poi editor if all you're going to use is the touchstrip, jog and the hotcue buttons ?
As with ANY new feature we add on the software, it must have a point that we believe it will benefit the users and their workflow. Also we don't want to clutter VDJScript with millions of commands for any possible "action" a user might want to do.
So, back to the subject: Why would you open poi editor if all you're going to use is the touchstrip, jog and the hotcue buttons ?
Posté Fri 19 Jun 15 @ 7:43 am
Dan (djtouchdan)
PhantomDeejay wrote :
I'm asking in order to understand. Don't take me wrong.
As with ANY new feature we add on the software, it must have a point that we believe it will benefit the users and their workflow.
As with ANY new feature we add on the software, it must have a point that we believe it will benefit the users and their workflow.
To give a real life example of exactly this is the Remote app.
Users were asking for access to Automix queues etc etc and the ability to add to them from the remote browser.
Initially the use wasn't understood. Someone explained the benefits and now its there in the latest versions.
Real life examples of use - make a huge difference in a yes or no verdict. Rather than just "i want to see this......"
Posté Fri 19 Jun 15 @ 9:04 am
Stretchincanada
Like!
Posté Tue 25 Aug 15 @ 3:05 pm