Post-Graduate for b71

[NPherno]

After getting my 'remix' of Xymantix's 'Gradudate' to a final form for 4.11 this weekend, I found myself wondering how hard it'd be to get Resizing in for b71. So, here it is. Playlist starts smaller than the 4.11 version, both to save space in the bmp files, but also because you can now size it up :) The 'bar' sizes in width, and the playlist sizes in both dimensions...

I was unhappy that adding a Width split to the playlist made the lower 'size' tab show a 'diagonal' resize icon... I wish there was some way to setup resize buttons that, regardless of their orientation to the split, could be forced to allow only 1 axis... UPDATE:: Fixed with Resize Edges (now able to resize all over the place!), reattached for those that care... now smaller (again) BMPs, PLUS, a normal resize button has been used for the lower-right corner of the playlist, to emulate a 'corner' resize... works like a charm :) ::UPDATE

Still, QCD has long been my favorite player, and it's a small complaint =-]

So, I'd love to hear what people think of this 'remix'... I have to say Xymantix created a _bad assed_ skin that I simply modified (at this point it's a pretty significant mod... but still, I didn't start this puppy). Small, simple, clean... just the way I like it.

NPherno

[Tokelil]

Nice skin (always has been). A tad to high for my liking since I like skins that has the same height as the titlebar. Anyway, I really like the vertical resizing of the mainwindow, (and that I have to drag it from the edge of the skin to resize, unlike phaseless 2.0 where I have to drag somewhere in the middle of the skin.)

:cheerful:

(Hmm why isn't the thumps-up icon in the Smilie List...)

[Rex_Mundi_Incarnit]

That's one sweet skin! :beer: :chinese:

[cudelleirbag]

Nice!

CL

[Paul]

I was unhappy that adding a Width split to the playlist made the lower 'size' tab show a 'diagonal' resize icon... I wish there was some way to setup resize buttons that, regardless of their orientation to the split, could be forced to allow only 1 axis...
In that case you should use 'edge resizers' instead of the specific resize control. The resize 'control' will always show the mouse cursor in the possible resize directions.

[NPherno]

In that case you should use 'edge resizers' instead of the specific resize control. The resize 'control' will always show the mouse cursor in the possible resize directions.

Well, who looks like the asshole now? (The answer is 'ME' if anyone isn't sure...)

Edge resizers... EXCELLENT IDEA. Yeah, just FYI, those work great :)

A few suggestions regarding the Resizing system before it leaves 'beta'... (normally, somebody at this point would say 'I'm no computer programmer or 'nuffin, but...', except I _am_ a PC/Console game developer with a decade under my belt & a specialty in graphics engines... so I tend to think I'm not asking the impossible/in-feasible... still, I could be wrong...)

Regarding BodyLimitSize/ExtXLimitsize ...

I don't want to limit the user of my skin... but I _do_ like the 'click & size' idea... why not add BodySnapSizeN/ExtXSnapsizeN, N being an number from 0-9. The setting is simply a 'snap' point in space... each click of a control sizes to the next snap up in size, until there are no more, and then falls back to the smallest. As a 2nd teir effect, dragging a resize 'past' a snap point in space causes it to 'snap' to it as QCD already snaps windows to each other/the desktop, unless shift/andor/ctrl is held, at which point snapping is disabled (which is already a feature, via shift, no?)...

At the current time, resizing is a full-resolution effect... a 1 pixel movement (ignoring snaps) is a 1 pixel resize... BodySizeStepX/BodySizeStepY / ExtXSizeStepX/ExtXSizeStepY could be created to allow the author to specify the 'step size' (number of pixels per resize axis) to force unless some override key was used (or hell, not overrideable)... as an example, since my skin's playlist has a 14 pixel entry height, I'd set Ext1SizeStepY to 14... dragging my skin's lower resize tab would never stop on a value that wasn't a multiple of 14... handy if you're tiling some skin inside the break-area and you want to be sure the user _always_ resizes to a multiple of that number as well (for those patterned backgrounds, etc)...

As an aside, it would be great if, unless disallowed via a setting (BodyNoFollowN/ExtXNoFollow), any 'edge' I am dragging that is currently 'snapped' to any other body/ext edge, causes the 'sibling' edges to follow the drag movement... which would allow for some very slick user-interaction... because I am sure few programs that 'snap' windows bother to try this, and it doesn't at all sound difficult... it'd make using my own skin when the body&playlist are sized to the same width & snapped together much easier, as I'd only have to resize 1. 2 windows snapped side-by-side that both resize would be resizable from their shared central edge, which also sounds pretty trick...

Anyway, just some pseudo-random thoughts!
N

[J44xm]

Butt-kickin'! :-) (I hope the time, which appears to be a static size, will show hours okay.)