Forum: VirtualDJ Skins
V8 but by FRUiT
Topic: V8 but by FRUiT - Page: 2
locodog wrote :
the potential of V8 skins.
That's the main goal of the skin. Thus it is in alpha stage, now I'm reducing and cleaning the xml as much as possible with the v8 engine. It will become a lot better.
locodog wrote :
I'm sat on an idea of having every dial slider and button as a custom so you can rescript more or less everything without venturing into the skin xml, I'm just waiting for the skin wiki
Yes I could imagine a "global edit" mode triggered by a button that would allow every buttons to be custimizable at once, the software being unusable while setting up buttons. With this edit mode, we would be able to set something on the rightclick of buttons (cannot now). Maybe in the future. Anyway the custom buttons are already awesome stuff.
Posted Fri 27 Jun 14 @ 12:37 pm
Posted Fri 27 Jun 14 @ 3:45 pm
Posted Fri 27 Jun 14 @ 5:20 pm
Posted Fri 27 Jun 14 @ 5:38 pm
In other words, have the right deck (red) on the left side of the screen ?
Posted Sat 28 Jun 14 @ 1:53 pm
Just my opinion though.
Posted Sat 28 Jun 14 @ 2:04 pm
Other question :
May the 'define' beacon have other parameters than 'classdeck' ? Let's say vars ?
<define class="someclass" condition="var 'somevar' 0"></define>
<define class="someclass" condition="var 'somevar' 1"></define>
Or whatever else than classdeck ?
Posted Sat 28 Jun 14 @ 2:44 pm
As a general rule if it can be used in an <element> then you can use it in the <define> as far as I'm aware.
Give it a try - :-)
Posted Sat 28 Jun 14 @ 2:52 pm
But, the class written below has ascendance on the class written above in the xml because both have the same name... So only the last one does exist when rendering the skin.
...Maybe I tried the wrong way, I'll give it a second chance.
The 'define' element is not described in the VDJscript_verbs page.
Posted Sat 28 Jun 14 @ 3:14 pm
Posted Sat 28 Jun 14 @ 3:37 pm
Posted Sat 28 Jun 14 @ 4:44 pm
Anything else that you put in there, they will be carried and added to the element when the class is called.
So if you add visibility to the <define> element, once this elements is called using class="its name" , it will be added to that element as well.
There is not any condition parameter or anything else other than the name and classdeck as mentioned above.
In case you need to use a different <define> for a button depending on a var, you need to name those defines differently (without visibility)
<define class="1stdefine" > ...</define> and <define class="2nddefine" > .... </define>
and display the one or the other like..
<button class="1stdefine" visibility="var 'myvar' 0" > ...</button>
<button class="2nddefine" visibility="var 'myvar' 1" > ..</button>
Posted Sat 28 Jun 14 @ 5:43 pm
The project was (is ?) themed buttons & sliders / colors, but without writing 5 times each button... Maybe a bit ambitious.
Posted Sat 28 Jun 14 @ 6:00 pm
Posted Sun 29 Jun 14 @ 4:49 am
0.2 is out
What's new :
- Code cleanup / bugs correction
- Dimmed on-screen scratch view
- Main Vu-meter color schemes (per deck - neutral - green)
- Return of the broadcast page
- Rightclick on 'sync' button does autosync-n-play
- Mirrored split waves mode
- Small other improvements
- Mixer's master tab new behavior (menu)
You may now change the mixer's master page using a small menu that appears on the master's tab itself when switching to it. At the moment there are a few pages (monitor - broadcast - sideview - sampler) but this behavior will me improved shortly to show several themed pages.
If you find some bugs don't forget to advise me !
TIP : The skin is extremely verbose using tooltips
Posted Sun 29 Jun 14 @ 5:43 pm
Posted Sun 29 Jun 14 @ 8:27 pm
When you change any skin, all the panels are resetted.
When you close the software, all variables are lost.
In my skin, some elements will stay even when closing the software, some others, not, depending on what I want to be reset. All of this does not depend on the skin itself, but software.
Posted Sun 29 Jun 14 @ 8:33 pm
@myvar : deck local persistent variable
@$myvar : global persistent variable.
The persistent variables are saved in the settings.xml
Also, if your panels are controlled by visible /visibility and variables instead of visible="yes/no" , the group=".." is not necessary to have
Posted Sun 29 Jun 14 @ 11:05 pm
Posted Mon 30 Jun 14 @ 6:18 am
djdad wrote :
Is this a 4-Deck or a 2-Deck Skin?
Posted Mon 30 Jun 14 @ 8:17 am