And, hello again. Cliff, do you have an ETA on even an early build of 155? I am basing the rest of the process on this implementation and there are deviation paths along the way based on how specific elements of integration work. Just a general, broad time frame will be cool, not tryin to pin you down to a day.
And this is quicker so will pose it here... Is there any particular reason that the skins "always' have the actual player image's buttons USED as the buttons? As in instead of a transparent layer just above the location on the WHOLE image? Here's why, I am not trying to make any skins from scratch, that isn't my forte. But, I am going to use product images of some of the musical tools that deadmau5 uses. As I am spending 20 hours a day on this build, and the art editing is what takes 90% of my time, it is hugely quicker to just put a layer over the spot i want for that function and be done with it. I am a paint.net user mainly, not PS and the plugins for PS suck ass, especially when there is any kind of effect involved. I have been using PS for all of these skins, for that reason, and my navigation of the app is not efficient. So if it is just a matter of a cleanly cropped button, Im just gonna do it my way. If there is some performance reason, then I will have to reconsider. Thanks.
deema Wrote:And this is quicker so will pose it here... Is there any particular reason that the skins "always' have the actual player image's buttons USED as the buttons? As in instead of a transparent layer just above the location on the WHOLE image? Here's why, I am not trying to make any skins from scratch, that isn't my forte. But, I am going to use product images of some of the musical tools that deadmau5 uses. As I am spending 20 hours a day on this build, and the art editing is what takes 90% of my time, it is hugely quicker to just put a layer over the spot i want for that function and be done with it. I am a paint.net user mainly, not PS and the plugins for PS suck ass, especially when there is any kind of effect involved. I have been using PS for all of these skins, for that reason, and my navigation of the app is not efficient. So if it is just a matter of a cleanly cropped button, Im just gonna do it my way. If there is some performance reason, then I will have to reconsider. Thanks.
the primary reason is probably for animation and visual feedback. it certainly functions to do as you mention, but the visible image would be static, no mouseover or pressed effects.
deema Wrote:And, hello again. Cliff, do you have an ETA on even an early build of 155? I am basing the rest of the process on this implementation and there are deviation paths along the way based on how specific elements of integration work. Just a general, broad time frame will be cool, not tryin to pin you down to a day.
Any moment now. Just finalizing the new installer tech and merging the last.fm plugin into the main program.
deema Wrote:And this is quicker so will pose it here... Is there any particular reason that the skins "always' have the actual player image's buttons USED as the buttons? As in instead of a transparent layer just above the location on the WHOLE image?
I think what he means is that many players use transparent 1% layers to extend the button trigger area so that they're easier to use. This is a convenience method and for elements that don't appear visually big enough to provide a comfortable trigger area.
deema Wrote:And this is quicker so will pose it here... Is there any particular reason that the skins "always' have the actual player image's buttons USED as the buttons? As in instead of a transparent layer just above the location on the WHOLE image? Here's why, I am not trying to make any skins from scratch, that isn't my forte. But, I am going to use product images of some of the musical tools that deadmau5 uses. As I am spending 20 hours a day on this build, and the art editing is what takes 90% of my time, it is hugely quicker to just put a layer over the spot i want for that function and be done with it. I am a paint.net user mainly, not PS and the plugins for PS suck ass, especially when there is any kind of effect involved. I have been using PS for all of these skins, for that reason, and my navigation of the app is not efficient. So if it is just a matter of a cleanly cropped button, Im just gonna do it my way. If there is some performance reason, then I will have to reconsider. Thanks.
the primary reason is probably for animation and visual feedback. it certainly functions to do as you mention, but the visible image would be static, no mouseover or pressed effects.
logokas Wrote:I think what he means is that many players use transparent 1% layers to extend the button trigger area so that they're easier to use. This is a convenience method and for elements that don't appear visually big enough to provide a comfortable trigger area.
Yes, exactly. Both reasons. Convenient to build and easier to click. This will be my method unless the buttons are/should be animated.
deema Wrote:And, hello again. Cliff, do you have an ETA on even an early build of 155? I am basing the rest of the process on this implementation and there are deviation paths along the way based on how specific elements of integration work. Just a general, broad time frame will be cool, not tryin to pin you down to a day.
Any moment now. Just finalizing the new installer tech and merging the last.fm plugin into the main program.
Cliff
This is great news. I don't know how the f I missed this earlier today......
Cliff Cawley Wrote:I've added support for this in Build 155.
Command line options are as follows: /SetMainPlayerPos=x,y /SetPlaylistPos=x,y /SetEqualizerPos=x,y /SetLibraryPos=x,y /SetVisualisationPos=x,y /SetMainPlayerScale=percentage
The player seems to be repositioned based on a relative setting, not an absolute one. It ends up in a different spot each time depending on the skin and/or possibly the scale of the skin from which it is being switched.