Xion Community

Sry Most of the hotkeys are mapped to the same ones i use for winamp, so i do not get confused - i didn't bother w/ hotkeys winamp does not has / are not enabled in my settings.
the alt+strg+enter is fine, so no need for a task button.

something else I've encountered yesterday -
-- Using 'Play now in Xion' for folders from windows explorer crashes xion after it askes me to save the current Playlist (Vista user)

-- The equlizer hotkey is mapped to ctrl+alt+e what represents the EURO symbol on most european keyboards. dunno if this is a good option.

Cliff, you missed something while changing shell integration.

'Open in Xion' is still available when right clicking on audio files.

logokas Wrote:Cliff, you missed something while changing shell integration.

'Open in Xion' is still available when right clicking on audio files.

No, not really. Its available because you associated that file. In order to remove that you have to unassociate the file format.

Cliff

martin.deimos Wrote:-- Using 'Play now in Xion' for folders from windows explorer crashes xion after it askes me to save the current Playlist (Vista user)

Is that a Vista Admin user or Limited user? Does it matter if you use one or the other?

martin.deimos Wrote:-- The equlizer hotkey is mapped to ctrl+alt+e what represents the EURO symbol on most european keyboards. dunno if this is a good option.

Yes, but you can customize these if you like. In the Global Hot Keys tab in Configure Xion. Select the Hotkey and then choose Assign Key or Disable it.

Cliff

Cliff Cawley Wrote:No, not really. Its available because you associated that file. In order to remove that you have to unassociate the file format.

How come you were able to remove them from folders, but not files?

That reminds me, still no 'Associate all' button :<

martin's crash seems to be exactly the same as mine, btw.

Oh and, i think i figured out why the playlist skin dies. You changed the skin psd's name, but didn't incorporate the default name into the playlist plugin. It tries to look for Default.psd, and gets the main skin instead of the playlist.

logokas Wrote:How come you were able to remove them from folders, but not files?

Its not a case of being able to or not. If I remove that, then it will remove the association. Its the same thing. If you don't want the 'Open in Xion' text on files, then you have to remove their association. Its the association that tells it 'Open this in Xion'. WIthout that, its no longer associated.[/quote]

logokas Wrote:Oh and, i think i figured out why the playlist skin dies. You changed the skin psd's name, but didn't incorporate the default name into the playlist plugin. It tries to look for Default.psd, and gets the main skin instead of the playlist.

If anything this was an issue in builds < 104. The playlist should be asking for default.zip?playlist.psd by default. If however you haven't loaded the playlist.psd manually still, from when the bugged build loaded the wrong file, then your playlist will still look broken. Have you opened the Skin browser, manually browsed to the default skin and opened the playlist.psd?

This will fix it, however there is another bug (which I've fixed for 105) which will load whichever skin you double click on in explorer.

Cliff

Oh now i get it.

Since i never shut off Xion, it never saved the change when i manually turned the playlist skin back to what it was supposed to be.

Onwards to new challenges then!

martin.deimos Wrote:-- Using 'Play now in Xion' for folders from windows explorer crashes xion after it askes me to save the current Playlist (Vista user)

I've managed to reproduce this one and have fixed it for the next build.

Cliff

wouldnt it be easier if the playlist had another suffix, or like the interface command, a simple "load playlist", where the suffix would make only the playlists available as choices, and vica versa, then ultimately, to discern between libs/playlists/skins/vis or what have you. It would be more like optional components.
xonenine.

Why should playlists be 'optional' ?

The concept of a music player is that you listen to music to it. While you don't need a playlist for that, you sure as hell need it to manage all the music you're actually listening to. It IS optional, by means of deleting the playlist plugin, but you'd have to be out of your mind to do this.

Perhaps you're simply not wording yourself correctly.

Youre right I could have said it more succinctly. I was thinking if vis/ playlist/skin/library/etc where to be differentiated via a different .ext or tag than they would all load with less errors. and in switching youd only see choices according to the component you wanted to see and switch.

xonenine Wrote:Youre right I could have said it more succinctly. I was thinking if vis/ playlist/skin/library/etc where to be differentiated via a different .ext or tag than they would all load with less errors. and in switching youd only see choices according to the component you wanted to see and switch.

They mostly do this now. I've left them all in the single skin browser though because people will find it confusing. They'll have to remember to open the skin browser for that particular plugin, such as the playlist.

In the latest builds if you use the skin browser and attempt to load a .psd with any of the layers that are specific to playlists, it will automatically tell the playlist to load the skin instead.

Anyway, I don't think its such a problem as the Beta builds stabilise.

I've actually been hoping more for feedback about making the playlist skin, not how its loaded, etc. I.e. is it easy to make, do things work as expected, but no one has given me any feedback

Cliff

Anything you want Cliff. I'll build several this weekend.
xonenine

When updating song information (ID3 tags), Shimmer doesn't update if the only change is in whitespace characters at the end of a string.

For example:

If I change "Nova" to "Nova blah" and hit "Save", the skin updates.
If I change "Nova" to "Nova " and hit "Save", the skin doesn't update. If I skip ahead a song, then back, the updated "Nova " is properly displayed.

pickle Wrote:When updating song information (ID3 tags), Shimmer doesn't update if the only change is in whitespace characters at the end of a string.

For example:

If I change "Nova" to "Nova blah" and hit "Save", the skin updates.
If I change "Nova" to "Nova " and hit "Save", the skin doesn't update. If I skip ahead a song, then back, the updated "Nova " is properly displayed.

Hmm I can't reproduce this. Shimmer should be trimming the string automatically. If I add spaces to the end, Shimmer never shows them as it trims the whitespace, hence the reason why it doesn't look like it updates. I've been unable to get it to display the space on the end, even if I skip to the next track and back.

Cliff