passionate-coder organization

passionate-coder ·

I've been digging around the source code, looks like I found those default paddings. I never realized the text padding was so small.

It looks like there may also be some references to the color bleed, but I can't tell if it's just referring to the glass...

Go for it. You have to try at least once.From my experience, though it just did the same bleeding thing.I'm sure way back someone tried using either 24-bit or 32-bit pattern image as well.It never went away. It must always be mixing with the system col...

That's an idea. However I think that the opacity should theoretically have nothing to do with the bleed, if we want the skin to solely rely on the supplied color and not the glass color. If it's the best solution, it could be worked with, but I also thin...

What about the way the menu color bleed goes away when the menu glass opacity is set to 0.

I wonder if there is a way that the coders could put an internal skin option that overrides the default 50% menu glass opacity to near 0%?So this would stop...

Acrylic would definitely be nice to have. Especially now, where it seems that Aero glass may be on its last legs with those flashes in the submenu. In general, I think there's a lot that could be done to "clean up" Open-Shell and its functionality, whether...

In most cases, I would just kill off the earlier skin by replacing it with the new version.This one is different. It's around 4 years old, and I'm sure the download link has been sharedby people and a few sites. I think the download link woul...

Good work! Looks closer and closer to the original Win7 menu.I have always thought that the search and jump views were defined strangely in Open-Shell, but as far as I can tell, there's no way to differentiate the font/separator. There is also the "Search ...

I decided to rename the skin with revB1 and now B2 because oh what the hay, I replaced the new selectors with the original on programs,small main, and the white submenu locations. The large main MS selector image needs conversion. I always have trouble w...

Hello
Oh shoot, I logged off here last night, but have been logged on on Github all this time. Oh well.

I misunderstood the search magnifier bitmap. Yes, it is more right.Not sure if it's worth changing as there is no way to make the search b...

HI

That's why it's called WIN7LIKE.
If someone wants a more original look with the exact Win7 code, then switch to Startisback.

The main reason I upgraded to rev B was to make the 2 column selector padding bigger,as well as adding a ...

I just checked out WIN7LIKE revB. Looks very nice, I like the extra space in between the main2 items, and it looks like you added many improvements overall. The new glass selector looks much better than I thought was easily obtainable. This is really n...

First of all, Iam very thankful for the productivity you have brought to windows, you have made win 10 to survive a couple of years further.
But, there is some small things I have on my wishlist :

As computer screens for a strange reason is 16:9 widescre...

I didn't notice any difference between classic and 7 styles.120 dpi just uses 16x16 pixels row in most cases, not the 20x20 row.And what's worse is depending on the type and size of the main font,the bottom row may or may not trigger for 144dpi. Ve...

A bit of a sanity check.When you set a classic style menu to 120DPI, which section of the bitmap does the search magnifier use?I just tested this with a couple skins, and for some reason they seem to be using the high DPI (bottom row) section of the bitmap...

Ok, I see. I'll probably change those going forward then.

I think it's a bug.
What we did way back was instead of calling it OPTION USER_IMAGE=#7014,0
we just used a different name like OPTION AVATAR=#7014,0
It seemed to work.

Question about the classic styles and their corresponding options.If I take a look at the "Metro.skin" file, I can see the options list and the options assigned to each style. However, there seems to be another factor at play for determining which options ...

I see how those menu_arrows.bmp get some of the directions in the SkinManager.cpp file:

static POINT g_ArrowSizes96[]={{0,3}, // insert left{3,6}, // middle size{6,9}, // insert right{10,14}, // right arrow{14,18}, // left arrow{18,25}, // down ...

I see how those menu_arrows.bmp get some of the directions in the SkinManager.cpp file:

static POINT g_ArrowSizes96[]={{0,3}, // insert left{3,6}, // middle size{6,9}, // insert right{10,14}, // right arrow{14,18}, // left arrow{18,25}, // down ...

There was one guy "meetHG" back on CSM who made Omni-Pic.skin7, that was like you,where he cut out everything to the bare minimum relying on the built-in defaults, then added what was needed.What would happen if you deleted all the paddings and see what ...

Interesting.I guess those defaults must be determined by Windows, because that's the only reference of defaults I found. It shouldn't be too hard to replicate, though. I am specifically looking for the defaults for submenu text and icons. I'll just assume ...

I don't really know, but my guess is it uses the empty skin defaults.
I found these files in ClassicStartMenuDLL in Classic-Shell-master 4.3.1

SkinDescription.txt

; Empty skin - all properties are defaults, except:

About=#7100AboutIcon=103Mai...

Hey, speaking of default stuff, there are default arrow bitmaps in there as well for 100 and 144 dpi.Did you ask if 125 dpi arrows can be updated/included along with the code to use them?Those internal ones work better(more functions)for the search arr...

I don't really know, but my guess is it uses the empty skin defaults.
I found these files in ClassicStartMenuDLL in Classic-Shell-master 4.3.1

SkinDescription.txt

; Empty skin - all properties are defaults, except:

About=#7100AboutIcon=103Mai...

I have a question about some default values. Do you happen to know the resource in Open-Shell that defines the default paddings? I'm trying to add some overrides and I want it to be precise as possible, then I will change it from there. I've looked around ...