Announcement

Collapse
No announcement yet.

Winamp Freeform skin engine bug thread

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • 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..
    Winique work-in-progress (download) | Stargate:Winamp - SG1 Edition | D-Reliction | wasabi.player skin (plague-edit)
    Winamp3_Default skin (plague fixes) | Opal Redemption | X-Slant | wa2skin.wac

    Comment


    • 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).
      ClassicPro© v2.01 : This plugin allows you to use cPro skins in Winamp. ClassicPro skins are all SUI skins and loads very quickly. ClassicPro skins is even easier to skin than Winamp Classic skins. A new layout have been added since version 2.
      Download ClassicPro© ==== cPro Skins ==== ClassicPro© Homepage ==== SC Forums

      Comment


      • any chances of System.setClipboardText(String _text) being fixed soon??
        Latest skin: fCrcl

        Comment


        • i think this was broken since early winamp3 days, but i might be wrong
          WebSite: www.skinconsortium.com - Community for Userinterface Design & Coding
          Skins: Click Here

          Comment


          • 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.

            Comment


            • 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
              WebSite: www.skinconsortium.com - Community for Userinterface Design & Coding
              Skins: Click Here

              Comment


              • 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.

                Comment


                • Sweet!
                  Looking forward to it.
                  Winique work-in-progress (download) | Stargate:Winamp - SG1 Edition | D-Reliction | wasabi.player skin (plague-edit)
                  Winamp3_Default skin (plague fixes) | Opal Redemption | X-Slant | wa2skin.wac

                  Comment


                  • Benski - is there a release date for 5.36 yet?

                    Comment


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

                      Comment


                      • 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.

                        Comment


                        • * 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.

                          Comment


                          • @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)
                            WebSite: www.skinconsortium.com - Community for Userinterface Design & Coding
                            Skins: Click Here

                            Comment


                            • 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.

                              Comment


                              • hm have you updated to 5.51 beta?
                                Sorry for being foolish. I have not. Sorry once again.

                                Comment

                                Working...
                                X
                                😀
                                🥰
                                🤢
                                😎
                                😡
                                👍
                                👎