Winamp Freeform skin engine bug thread

[Plague]

yea well, I have the problem of either getting like 5 items of the same thing, _or_ when a command is disabled, the next time I create the menu (on a completely different object) that command won't show up at all, even though it's run through the same checks!
I have no idea why that happens, but it does..
I have created the menu just before it's shown, it doesn't help..
I don't know why, but it just won't work..

So I've settled with another crappy solution instead, that does what I need, but it won't disable the commands at all unfortunately..

[pjn123]

Benski...
Since you're looking here...

Can't you maybe try to fix some of the bugs that are demonstrated in >this< skin? Sure it won't take to much time.

And. Is there anything in the pipeline that we should get excited about, skinning wise that is. (Maybe a roadmap)

Mr Jones: We all know your eP is big, but not as big as Benski one (And that's when he fold it in half).

[RandomCarpet]

any chances of System.setClipboardText(String _text) being fixed soon??

[martin.deimos]

i think this was broken since early winamp3 days, but i might be wrong

[Benski]

Originally posted by RandomCarpet
any chances of System.setClipboardText(String _text) being fixed soon??

Just fixed it. Looks like it got broken when the port to linux was done early in the winamp3 days.

[martin.deimos]

Thanks, Ben!
perhaps a getClipboardtext() would also be a cool feature!

Btw, i tried to setup the winamp3 4 linux on my Suse 10, but no chance... nevertheless i can wine winamp5 or use the winamp clone

[Benski]

Originally posted by Plague
this bug, although reportedly fixed, is still showing parts of it's ugly face.
there are no more crashes, and the gradients aren't ugly as hell on resize anymore...

However.. If you try the wasabi.player skin linked in the quote, and start resizing a window, you'll see how the right side of the titlebar gradient will start to disappear more and more, and after a while only be shown if you make the width of the window very wide.

So, I guess the bug isn't completely fixed after all...

OK this is really fixed now (for 5.36). I was thinking the problem was in <bitmap filename="$gradient"/> but really it was in the <gradient/> object (argh!) Once I realized what was going on, it was a pretty simple fix.

[Plague]

Sweet!
Looking forward to it.

[JW]

Benski - is there a release date for 5.36 yet?

[Mr Jones]

When it's ready generally is the usual and expected answer.

I found out that something is wrong with the <rect/> object. The edges parameter does not work correctly. First, according to this site, the edges should be separated by a pipe (|) but that doesn't work. Instead, the semicolon (;) does work. Weird.
But, that's not all. If you use edges="left;right", the entire left side is shown, but only the right side without the top pixel and bottom pixel. I guess they belong to "top" and "bottom", but it would be better if the corner pixels belonged to both left/right and top/bottom.

[E-Trance]

* OS cursor support
you can define os cursors via cursor="IDC_*" as param for button, layer, ...
IDC_ARROW, IDC_SIZENS, IDC_SIZEWE, IDC_SIZENWSE, IDC_SIZENESW, IDC_SIZEALL, IDC_IBEAM, IDC_WAIT, IDC_CROSS, IDC_UPARROW, IDC_NO, IDC_HAND, IDC_APPSTARTING, IDC_HELP
moreover, <layer/> object should now also respect the cursor= param

Seems to be fake because I just can't get OS cursors working Though element-based cursors work well.

[martin.deimos]

@E-Trance:
hm have you updated to 5.51 beta?
here you see bento with a hand over the mcv entrys. the otherones should work as well.

@Michgelsen:
Consider to use 2 rects w/ w="1" instead of one. so you can create your design as you like. Changing this behaviour might break some of the other few rect based skins.
Hint: you can create a $poligon, $gradient and $solid image direct via element defienition (see wasabi.player base skin)

Originally posted by martin.deimos
Consider to use 2 rects w/ w="1" instead of one.

That's what I did, but it kind of feels like a workaround.

Originally posted by martin.deimos
Hint: you can create a $poligon, $gradient and $solid image direct via element defienition (see wasabi.player base skin)

I have no idea how that works but I'll have a look, thanks.

[E-Trance]

hm have you updated to 5.51 beta?

Sorry for being foolish. I have not. Sorry once again.

[SLoB]

think setAlpha is borked on layers derived via classes

does not seem to work yet other derived classes work for other objects.

for example

Class Layer mylayr;
Global mylayr thislayer;

thislayer = yourlayout.findobject("gotthislayer");

mylayr.setAlpha(70);

[pjn123]

Does .setXMLParam("alpha", "xx") work?

[SLoB]

ah yea forgot bout that 1 sylvester, but that does not work either they both should work regardless

[Plague]

I've created my own bugs and wishes thread, since this one is filled with more than just bugreports and I wanna make sure it's easy to find my lists and that they they won't be lost in a sea of regular posts and comments.

anyways, here's the link:
Plague's wasabi freeform engine bugs and wishes

[E-Trance]

It seems that main menu in Bento tends to lost translation after switching beetween Small and Big Bento several times (1-3).

[E-Trance]

One more bug...

Skins can't determine the number of channels in a localized version. That's because of translation of Stereo/Mono to something else. Can you introduce something like isStereo() or even getChannelsConfig()?

[E-Trance]

Another bug...

getTextWidth() always returns width of an untranslated string. For example, text object with default="Artist" will display "Исполнитель" if translated to russian. That is much longer than "Artist". Though getTextWidth() will return width for "Artist" and not for "Исполнитель".

Ohh... Even more! getText() also returns untranslated string.

[pjn123]

Use getAutoWidth()...

And the getText() isn't abug... It must return that. If thats changed some maki scripts will brake. They need to add a new function like getFinalText() and they need to to add a function to maki that sends a string through the translate system so that you can use it for something like "Volume: 78%".... Can then just do something like this: translateString("Volume")+"78%"

[E-Trance]

PlEdit.getLength(int item) returns only a number of minutes w/o seconds. It's just useless and it's a bug. Isn't it?

[Lion_S]

very nice

[VIPer]

PlEdit.getLength(int track_num) returns only minutes instead of milliseconds as getPlayItemLength() does. For example it returns just "7" if length is 7:28. Please fix it.

[martin.deimos]

have u looked at the api??
getLength returns a string and not an int!
so a return value looks like "3:48"

[VIPer]

The prototype was:
extern int PlEdit.getLength (int item);

It seems that there was a file with error somewhere. It works fine after fix to "string". Thanks.

[martin.deimos]

ok maybe u have a wrong pldir.mi file - the 5.55 development took so long so i have no idea what's fixed / new or what was already in 5.54