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 Installer Version:
r2 Studios Server -> http://www.r2.com.au/downloads/files/beta/qa-xion_v1.0b90.exe
OR
Xion Server -> http://xion.r2.com.au/download/beta/qa-xion_v1.0b90.exe

Changelist:

• Fix snaprectangle being picked up and blocking mouse clicks
  
• Fix crash when visualsation layer has no data
  
• Fix VolInc and VolDec not having _over and _down states
  
• Fix Animation layers allowing clicks to go through them to layers below
  
• Add support for Track Number display both in the File Information as well as in track skin displays
  
• Fix bug when id3 tag genre is saved as out of range value, that it gets Blues assigned

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.


ABOUT THIS BUILD:

Getting pretty close to a Public release now! Please test all previously reported issues on your end as I'm fairly sure they're now fixed! Please let me know if you see anything! Thanks everyone!

Enjoy!

Cliff

wooh, at first sight this seems to be working very fine

all things are working fine and: it takes some less CPU!

took few time to test, which means: positive- for me

nah it can't be lol

will check it out tomorrow, didn't even bother to test the last build, as soon as i saw the few bugs innit heh

SLoB Wrote:nah it can't be lol

will check it out tomorrow, didn't even bother to test the last build, as soon as i saw the few bugs innit heh

Aww, don't do that. If you find bugs that others haven't found, then it means I can fix EVERYTHING for the next build, instead of just bits and pieces over MANY builds!

The bugs that were there didn't have large impacts at all, it was just special cases.

I'm stopping further feature adding for now, until the major bugs are fixed, so please test this build! Even if some people report bugs, please still test as you may find more that I can fix all at once!

If this build goes well, I'll release the next build to the public

Cliff

ALAS Wrote:wooh, at first sight this seems to be working very fine

all things are working fine and: it takes some less CPU!

took few time to test, which means: positive- for me

Sweet! This time I performed a Release build so that all optimizations were applied, instead of the usual Beta build that still contains Debugging information.

If Xion crashes in Release, there will be no Crash window as I can't get anything useful from it in Release mode anyway

Cliff

ok a few things broken in this build, clean install

passthrough not working on layers within sets (even though the layers within themselves have passthrough keyword)
moveable also not working on layers within sets (even though the layers within themselves have passthrough keyword)
for an example see shift 1 or 2 skin and try and click on the buttons or songticker under the glass, also try and move the skin on shift 1 on the metal parts

volumelr or buttons not working due to the above (they will work if the above is fixed)
tooltips not working on random, repeat, mute (think the over state is blocking the tooltip from triggering, works if you move the over state out of the way, the tooltip is then triggered)
for an example see Graviton skin

the main ones are the passthrough and moveable not working, they were working fine in previous builds

could confirm something- well - similar to what SLoB described

testet Rupert..

to my experience:

random, repeat and "button" don´t work (at all) as long as there is SOME layer set above them, regardless if passthrough or covering their area with pixels

also: that way play and stop are affected by layers above them when linked to indi_whatever...

previous, next, pause, playlist and mini work well

concerning moveable: the moveable tagged layer is not moveable everywhere, there are areas where you can move it and others where it is not possible (there´s nothing - with pixels - above areas which are not moveable)

on the other hand: parts of an animation set for volume (headphones) are responding to moving although not named moveable

(all experienced with Rupert)

P.S.: some observation here: seems like all things in the lower part work whereas things in the upper part don´t, shurely is conincidence for this skin, though wanted to mention it...

Hmm, ok thanks guys, I'll check this out soon. I thought I'd fixed all instances of these problems, but I guess not

Cliff

Hi Cliff, just want you to know the new beta works awesome with all skins so far for me on Windows Vista home Prem. I am still skinning Sonique skins, and have an awesome collection of nice vis. But now that I've seen Xions capabilities, I'm hooked, with or without vis, this adds a whole new dimension to enjoying skinning. Thanks!

Speaking of another whole dimension, could this ever be coded to be a spinning cube with access to all 6 sides? (even in a window maybe) Anyway thanks again, I live for this @#$%.[/img]

Later: I'm already sure it could be done as animations, with some hard work.

Cliff Cawley Wrote:Hmm, ok thanks guys, I'll check this out soon. I thought I'd fixed all instances of these problems, but I guess not

Cliff

hmm well it is such a lot of functionalities that Xion has these days, I think it´s hard to keep control for every one of them when you only can test them with complex skins out there containing stacked animations, invisible hot spots, and and and.. .

My suggestion is that we make some diagnostic skins, each representing a certain set of functionality (also in combination with another one), with simple demonstrative graphic elements (eg showing next_over in words, or triggered animation layer xy in words, or play button covered by passtrhrough layer in words, just some simple examples), like the ones I sent to you for bug diagnostics those days. This set of skins then should represent everything that HAS to work basically for Xion.

Also those skinners here who developed certain special techniques could make such diagnostic skins containing this technique for testing (eg my pseudo buttons).

Maybe it would be easier then to systematically check for all functionalities and for tracing bugs instead of having to test tons of complex skins out there...

xonenine Wrote:Hi Cliff, just want you to know the new beta works awesome with all skins so far for me on Windows Vista home Prem. I am still skinning Sonique skins, and have an awesome collection of nice vis. But now that I've seen Xions capabilities, I'm hooked, with or without vis, this adds a whole new dimension to enjoying skinning. Thanks!

Speaking of another whole dimension, could this ever be coded to be a spinning cube with access to all 6 sides? (even in a window maybe) Anyway thanks again, I live for this @#$%.[/img]

Later: I'm already sure it could be done as animations, with some hard work.

Hi xonenine and welcome to the Xion Community!

I look forward to seeing some of your skins!

As for the 6 sided idea, it shouldn't be too difficult. It will require some slightly advanced knowledge of the layer keywords, but with a little practice and some questions if you run into problems, you should definitely be able to do it

There are some already existing skins that have 2 sides, that flip between them, which you can always download and extract to learn from!

Cliff

ALAS Wrote:

Cliff Cawley Wrote:Hmm, ok thanks guys, I'll check this out soon. I thought I'd fixed all instances of these problems, but I guess not

Cliff

hmm well it is such a lot of functionalities that Xion has these days, I think it´s hard to keep control for every one of them when you only can test them with complex skins out there containing stacked animations, invisible hot spots, and and and.. .

My suggestion is that we make some diagnostic skins, each representing a certain set of functionality (also in combination with another one), with simple demonstrative graphic elements (eg showing next_over in words, or triggered animation layer xy in words, or play button covered by passtrhrough layer in words, just some simple examples), like the ones I sent to you for bug diagnostics those days. This set of skins then should represent everything that HAS to work basically for Xion.

Also those skinners here who developed certain special techniques could make such diagnostic skins containing this technique for testing (eg my pseudo buttons).

Maybe it would be easier then to systematically check for all functionalities and for tracing bugs instead of having to test tons of complex skins out there...

This is true, I have a Tests directory where I have a bunch of things to test, but alot of skinners have come up with new and interesting ways to make things which I don't have Tests for

Cliff

ALAS - I was also thinking that we could have some test skins too lol

I was almost going to mention it in my last post as I thought its all very well spouting of this and that skin, ideally all techniques should be in one skin, it doesnt have to look pretty it just has to have the techniques in there so they can be easily checked

I think we need this test skin, especially for Cliff so he can easily test functionality that we have come to expect from Xion so far, due to C++ being unmanaged code its harder to put in unit testing and not having traffic light build errors does not help breaking functionality even accidentally.

perhaps we could all work on the same skin and pass it round the skinners that want to get involved with it, should keep it a fairly small number but so that those with techniques that try and push Xion can have a diagnostic skin with all the bells and whistles.

I was thinking a biggish skin, with nice and clear labelled techniques and buttons, each part with its own functionality sectioned off, but also some overlap so that we can also catch the latest issues

ALAS Wrote:could confirm something- well - similar to what SLoB described

testet Rupert..

to my experience:

random, repeat and "button" don´t work (at all) as long as there is SOME layer set above them, regardless if passthrough or covering their area with pixels

.. SNIP...

P.S.: some observation here: seems like all things in the lower part work whereas things in the upper part don´t, shurely is conincidence for this skin, though wanted to mention it...

OK, ALL of these issues was caused by ONE problem. The problem was that animation layers were being accepted if they were not visible for the mouse.

I made a single change to ensure that animation layers weren't returned if they weren't actually visible (A bug I'd recently added)

This one change has fixed ALL of the issues that you and SLoB reported!

What you were experiencing was just side effects

Thanks ALAS and SLoB!

Next build coming up soon

Cliff