Xion Community

WARNING:
This is a Beta Build. That means it has fixes and features that are NEW. It is also possible it has bugs that are NEW! If you are looking for stability, please don't expect this build to be perfectly stable. It may have issues. If on the other hand you are happy to try this build out and post any bugs back in this thread, then please do!

Download:
r2 Studios Server -> http://www.r2.com.au/downloads/files/beta/qa-xion_v1.0b62.exe
OR
Xion Server -> http://xion.r2.com.au/download/beta/qa-xion_v1.0b62.exe

Changelist:

• Add ability to delete and open skins from a context menu in the Skin browser
  
• Mod resizing of windows to use the base class rather than overridden values. Playlist is now sizeable to a lot smaller
  
• Add a bunch of changes to do with visibility states so that loading and saving states works better

If you find bugs specifically related to this build, please post them here instead of the Bug reporting forum. Any feedback positive or negative should also go in here, no new threads. This way all feedback, etc related to this build will be in the one place.

NOTE 1: I've changed a fair amount of the logic to do with hiding/showing the layers to get this to work. The changes MAY break your skin. If it does, please LET ME KNOW! If it doesn't break your skin, then no worries, no need to let me know, just if there is a problem.

NOTE 2: You *may* have to set some of the layers visible that you normally left invisible. I.e. The visualisation layer now correctly obeys the visible state so that you can trigger it using a command and have it hidden to start with. The same with the indicator objects.

NOTE 3 (eee!): If you have previously used the state_save keywords, you *may* have to delete you Xion\States directory in order to stop Xion from crashing. This is a beta release and since these features aren't being used by the general public I will put the version stuff in for the next build. For now this build is to check the new Visibility code.

Enjoy!

Cliff

savestate & tt works a treat now Cliff, thanks
the only issue i saw was that the pause_normal indi_play layer needed to be set to visible, whereas previously it was always set to invisible, not sure if that was correct or not to begin with tho

muchos configurable stuff available when the next release comes out whoop

Yup, pretty much any indicator layer that you previously hid, will need to be shown if you want it to show up straight away. This is so that you can use buttons to turn them on and off as with other controls.

I've noticed some other interesting side effects with this new way of doing things, which I am finishing off at the moment. It is to do with putting layers in layersets and Xion thinking they are always animation layersets, no matter if they contain the keyword or not.

So if you anyone out there has layers within a layerset that is not an animation set, may notice their layers not showing up correctly. This issue will be fixed for build 63.

If that confuses you and your skin works, then sleep through until build 63

Cliff

Xion seems to be caching the skin somewhere, tt(x) have been changed for description but still shows previous wording despite closing Xion, deleting both preview, states

this is for both xsf & psd, tried both to see if it made a difference

tooltip(x) however does change the description but tt(x) seems to inherit last known value

oo, almost forgot this

Balance on the prefs screen, this looks as if it was made to look similar to the volume as far as gui wise goes, however there is no center click, ive opened up the settings file a few times to check the balance figure and its possible its not always zero if using the slider

a few ways it could be better and more accurate, add center click/pause and or make the slider wider or add a center click/button

In my skin (TriggerDisk) the animation for opening the interface was defined as:

layerset: animation id(trigger) delay(0) animtype(1) paused
first frame: Trigger00

with the first frame of the set visible in Photoshop. In this latest build I had to modify this to make sure the first frame was visible on initial load of the skin:

layerset: animation id(trigger) delay(0) animtype(1)
first frame: Trigger00 modify(trigger) action_anim_stop

Was this expected behavior?

Harkonenn Wrote:In my skin (TriggerDisk) the animation for opening the interface was defined as:

layerset: animation id(trigger) delay(0) animtype(1) paused
first frame: Trigger00

with the first frame of the set visible in Photoshop. In this latest build I had to modify this to make sure the first frame was visible on initial load of the skin:

layerset: animation id(trigger) delay(0) animtype(1)
first frame: Trigger00 modify(trigger) action_anim_stop

Was this expected behavior?

No, this definately smells of a bug to do with the new code. I will look into it tonight, thanks for the report!

Cliff

nice stuff, cliff!
too bad that i havn't time to take a closer look at xion skinning atm!

think its been mentioned before
download xsf skin to desktop, open it and Xion opens the skin, however the skin is not copied into the xion interface folder nor a preview made for it (the interface path in settings.dat is to the desktop)
with that skin still open then goto choose skin and it crashes, first off the choose screen is blank with approx 50% cpu then it goes bang after a short while
looks as if it defaults to looking at the desktop for skins rather than the Xion interfaces default?

SLoB Wrote:think its been mentioned before
download xsf skin to desktop, open it and Xion opens the skin, however the skin is not copied into the xion interface folder nor a preview made for it (the interface path in settings.dat is to the desktop)
with that skin still open then goto choose skin and it crashes, first off the choose screen is blank with approx 50% cpu then it goes bang after a short while
looks as if it defaults to looking at the desktop for skins rather than the Xion interfaces default?

Cool, thanks for the report, I'll nail that one for the next release

Cliff

martin.deimos Wrote:nice stuff, cliff!
too bad that i havn't time to take a closer look at xion skinning atm!

Thanks!

No worries, when you can

Cliff

Thinking of the missing first frame, and making workaround putting a copy of the first frame beside animation, I thought of a probable feature (I think that this is a better thread than "request feature" for it).
There are lots of new animation types. What if make a visible layer, named "alt_animation" and put it above the animation. When an old version (that doesn't know the animation) comes across it, it does nothing, but the animation is hidden by the layer, when a new version comes to the layer, it hides it if recognizes animation type and animation is visible. (backward compability).

And it is not good that not visible (in PSD) indi_layers don't become visible when the event happens.

A quick question Cliff, are you going to do so we can shrink the witdh on the playlist? It is little to big

check build 62, its shrinks down so small to be unusable lol

wow so many beta builds already, Cliff is spoiling us
*goes d/l himself a new beta

btw, when's the next official build? would love to release a skin that has all the awesome new features in it