Jump to content

aphelion

Member
  • Posts

    74
  • Joined

  • Last visited

  • Donations

    $0.00 

Everything posted by aphelion

  1. Noel, these clearly contradict Apple's human interface guidelines for the height of buttons to be at least as tall as a thumb. What kind of monster would design such an interface? You must have no regard for humanity, usability, or thumbs.
  2. I haven't tried AutoIt but have had no such issues with AutoHotkey
  3. Here's my themeatlas modded from Snowy8Glass. It's resource name STREAM name 986 language 0 if you're using Resource Hacker to change the msstyle. Or you can apply using the ThemeAtlas reg entry from AeroGlass. The entire file is different so there is no overlap with the original Snowy8 other than inspiration so I think it's ok to post here. Note I just tweaked the maximize buttons and they're alternatively either pushing up on mouseover against the close button, or going 1 pixel too far down. I'll track it down eventually but welcome contributions. http://i.imgur.com/4L7jcaw.png
  4. That would only be theoretically possible with a custom unsigned theme, since it can have a different stream used for the atlas. The default windows one doesn't have enough room to put a glow
  5. There's also a helpful guide png in the theme atlas thread that shows some very general sections. But for reversing 2 colors, it's fairly straightforward just by looking at the atlas in photoshop. Wherever one color is, put the other, and vice-versa.
  6. Noel, check out my theme atlas in that thread for a glow that is both white and dark at the same time depending on what's behind it. Edit: Link to PSD if it helps
  7. clownoutbreak.com, really? hmm.. Edit: And gotyoursoul.com?
  8. It's probably a font substitution issue (since the taskbar is messed up too.) Try restoring the attached keys. DefaultAllFontKeys.reg Edit: If that doesn't work try restoring the font links: HKLM.FontLink.backup.reg Edit 2: Last resort, http://www.withsteps.com/2621/windows-8-default-font-download-repair-kit.html
  9. I think it's applicable. The term is used in most of philosphy as way of defining rationality. Probably off topic though, and yes, you are free to jump off the island any time, but no island's terrain is going to be perfect (or is it?)
  10. Also, nothing we say or do can change the fact that Microsoft won't change a thing. Microsoft is the terrain here and that does not change. We all are navigating the same course, and I struggle to find sense in focusing on what bumps the road has.
  11. Sorry, that came off harsh. If you don't want to forego the color altogether, then those TTF fonts optimized for ClearType are going to end up looking bad on any screens that are not either RGB or BGR (the limitation of PixelStructure besides grayscale.) The tuner does allow you to change the degree of color intensity which is reflected in the EnhancedContrastLevel registry value (I don't recall whether that's respected with the Segoe-esque fonts or not, but I suspect not.) The reason I'm recommending removing color altogether is that this is the direction Microsoft has already chosen as the future of ClearType through DirectWrite. It's different than using grayscale rendering or disabling font smoothing altogether. Instead it resembles the rendering of OS X a lot more, widely considered a superior font rendering platform, without losing much of the subpixel antialiasing that the colors were creating. In truth, there really aren't subpixels in the first place. It's a distinction between the cones and rods in the back of the cornea that can distinguish between luminescence and hue. The brightness/luminosity will always be caught first and the hue provides additional details, and in that sense it sorta-kinda creates this illusion of subpixels, but that's not really a thing. It does exist in the panels, but ClearType does not take advantage of the hardware in the way it claims it does-- that is, using those 3 separate colors in varying levels of brightness to provide greater resolution. It just isn't possible through software. It simulates it, but it's not the same thing. The DirectWrite method does have the benefit of supporting every rotation (not just RGB or BGR) so while it's being adopted on one hand for tablets/handhelds, there's more to it than just a loss of color. It's very finely tuned to provide the same resolution you're used to with ClearType now, without attempting to simulate subpixel antialiasing and creating all sorts of distortions in the process of using color to do that. It's a bit of an upgrade to ClearType more than anything else, since it ultimately is more widely supported and looks much, much better than either grayscale or aliased rendering. If you want to experiment with the different types of rendering there are 2 great tools, one is a Firefox plugin called ClearType Tuner or similar, and the other is the MacType Wizard which lets you set granular control over color to an extent far beyond anything available in Windows native font rendering. It applies system wide in Windows if you choose to use it, but it's also a good informational tool to see what's happening with the various ways. Basically it's the ClearType tuner with a thousand more options, and they choices you make are actually respected system-wide. There is a toll on resource use, primarily keeping the glyphs in memory but that shouldn't be an issue with your setup.
  12. A complete fix is possible, though. You're getting lost in the weeds. Check out some of the screenshots I've been posting. No color fringing anywhere--taskbar, notepad, explorer, etc. The way it's done is by a combination of: 1. ClearType Tuner set to PixelStructure 0 2. CU WindowMetrics all set to use OTF with PS outlines (Myriad Pro comes in many forms) 3. LM FontSubstitutes that previously pointed to sans serif changed to point to the same OTF 4. Resource strings in the Windows Theme changed from Segoe UI to the same OTF (.msstyles String Tables and shellstyle.dll HTML) 5. Edge case: Photoshop needs "drop shadows" disabled in its UI fonts to remove color fringing I am not modifying any registry settings manually or disabling ClearType--grayscale seems like it loses all tracking. Another way to go about it is MacType but that's a sledgehammer I suspect you don't want to use.
  13. Yeah I get it, and as you said the shadow resource doesn't get the color tint, so that's why I proposed a color agnostic solution. It's the only way that it can be ubiquotous, so that it works for everyone regardless of theme or color settings. If it's done right it can still look good which is why I showed the screenshot--there's no need to have 2 borders on my windows, but it doesn't look bad at all.
  14. Another way to restore borders is in a color agnostic way. I'm on 8.1 but this screenshot shows 2 pairs of borders, the second is generated by the shadow resource and is clear so it won't conflict with whatever the desktop or theme color is.
  15. Isn't that the same look when you run an app in compatibility mode for a previous version of Windows? I'm not sure if it's aerolite or just something for compat mode but I've seen it in Win8 before
  16. Assuming you mean 8.1 there is a home. Win+S was killer for me when upgrading to Win8 since I use voidtools Everything Search. It's like 100x+ faster. So I disable all Win+ combos and re-create them in AHK. The CLSID you posted was useful to re-create Win+E
  17. It was that plus the privacy. Things like steps recorder creep me out. Anyway I culdn't find it, but I did get it working using by restarting WinSAT and re-running the test. winsat formal -restartpowershell /c Get-WmiObject -Class Win32_WinSATThat way also gives a good look at the progress with about 3 pages of output. I'm all around 8.5 on a recent OC'ed Haswell re-build. Hardly accurate since I notice the speedup in daily use and it was something like 7.8-8 before, on Bloomfield, some 8 years old. I remember when a 2-gen upgrade would yield scores 3-4 points higher, so perhaps part of the reason it was removed was because it skews low. Edit: Re-running through perfmon after this shows the scores
  18. Manual and running here also. I'm sure it was a GPO, I'll look deeper since the filter isn't catching it
  19. Hmm.. I'm coming up with all 0.0's. I thought I had disabled a GPO for "Enable PerfMon" but can't find it (to re-eanble) by filtering the policies or searching online. Ideas?
  20. The CLSID launch works on Win8.1 too. I use AHK for selective Win+Key combos
  21. I can send you the patched file if you PM me or enable PM's or you can use any resource editing tool. I used Resource Hacker. The changes are made to GlassSnowy8.msstyles
  22. Did sfc fix it? The log is divided into Info, Warning, Error, etc. Search for Error and that will point you to where it replaced stuff.
  23. Yeah well, this stuff gets driven up the chain by a combination of haphazardness on the side of developers and zeal on the managers looking to put a gold star in their presentation. In a perfect world it'd be all thought out from the beginning, but the implement-first culture reality is that they'll get it right eventually and we'll just have to wait or find ways to work around. I find that as I get very tired (over 20 hours or so) my brain starts to forget the familiarity of the screen and I notice the bands come out more, as well as the overall display looking more "liquid" if that makes sense. Conversely, CRT I see a screen door effect between pixels. Joe Sixpack doesn't use the 'puter as much.
  24. They're kinda-sorta just starting to get there. The DirectWrite implementation of ClearType removes the subpixel color based enhancement in favor of a grayscale one precisely for the reason jaclaz mentioned: because handheld devices can rotate and their pixel structures shift rapidly without any way to know how they're being looked at to optimize the font rendering. Also there are various studies that show about a third of the population notices color fringing significantly more than more people and for them it's a distraction rather than an enhancement. It's probably related to the degree of variance in astigmatism -- the most common is on an axis of 180 deg and the more you have the more likely you are to have your subtle visual boundaries drawn on a vertical axis that brings out those band of color. This is on a very microscopic level though, and since it's not the majority of the population Microsoft is just waking up to the annoyance their value-adding is causing.
  25. Yeah as others said I'd have just posted on the forum instead of calling India, generally we're more likely to be able to help. I'm a Gold + Cloud Partner and have an MSDN Ultimate subscription and don't mind sharing to help a fellow in need. Edit: I don't even bother calling MS anymore, my last time was the deal breaker. I called about an Office E3 Developer subscription and they kept bouncing me back between Partner -> MSDN -> Office -> MSDN. For 2 weeks I waited (it was a really simple, simple thing that Azure had done for me before in a day) and I told them to forget it. They said they'd consider it a complaint and log it. I'm sure they're still on it. And that was with "priority" support out of Bellevue.


×
×
  • Create New...