JRSCCivic98

Previous versions allowed for a highlight/copy/paste... didn't they?

I know we ran into this when WB5.x came out. Can you please tell me again specifically what causes this when you have WB loaded? Also, obviously Aero doesn't have this issue, so what's different in the way Aero skins vs WB6? Thanks.

If the system has XP SP2 on it there's a startup choice when you hit F8 which supresses the restart on error. The problem is the system is bluescreening and rebooting like it's set in the startup options. If you don't see Disable Automatic Restart or something like that when you hit F8 you're guaranteed it's SP1. Can't be older then that unless you've never updated XP on this box and you got it more then 4 years ago... highly unlikely. You need to find out what the bluescreen states first be

I do not skin (don't have the time for it really), but I help people develop software and skins for various platforms. When I find problem I report them and expect them to be fixed. I don't expect excuses for not being able to fix them. I know some things depend on the OS for the "capability", but undoing certain things to be able to do others (like breaking the CMD skinning) I don't like. You should never have to break something to make something else happen. If you have to subtract to "ad

Hell man, not all my reports end up being a "SD was right and I was wrong" so shove it already. Anyway, it's amazing how it took 6 pics (which I didn't post) to finally see the redraw problem on the Start Menu under Aero itself. Obviously this is because of the coloring choices of Vista, but up until today I didn't notice it. If the combination of WB6 and some of their skins wouldn't have made it so blatant I probably still wouldn't have noticed it. Hell, I had to get super close to the scre

Yeah, my post was about wbconfig. It's kind of anoying that it applies on the fly for choices like that, but the skinning apply does not. It messes with me and I'm sure others as well. How hard would it be to keep it from doing the "on the fly" option changes?

Ok, I took several close looks again and it does happen in Aero as well. (You do have to look REALLY close though, I mean REALLY close.) My bad. I'm taking this up with MS then. However, my concern about the All Programs/Back (+ arrow) still stands and I'd appreciate Neil allowing for this sort of menu display to happen when skinning in WB6 and to update all Stardock official skins to work like this. I think it would make for a "more complete" product. Also, another request for capabilitie

If you go into WB6 and let's say just go into Coloring and put a check in, but don't click on Apply Changes but instead close the program with the X, the checkmark choices are still kept. This is nasty because if you make a change you don't want to keep the easiest way in "All Window's History of Programs Every Made" a simple Cancel or in this case a close of the program prior to clicking OK or Apply would revert the changes back. Why doesn't WB6 behave this same way? It gets really anoying w

I've noticed sometimes if you maximize and minimize quickly via clicking the program taskbar tab it will mess up the animations unlike Aero. You can do this very quickly in Aero, but when WB6 is skinning sometimes the animations work, but sometimes the maximize just appear as a full screen repaint instead of the actual Aero animation. You guys notice this also?

I'm sorry guys, but on my laptop's Aero does not corrupt the shifting. I don't know what you're talking about or trying to blame on Vista's GUI capabilities at all, but WB6 corrupts, Aero does not. I'd post some screenshots, but this forum doesn't allow for image upload and I don't feel like hosting them elsewhere. Hell, I tried it on 5 PCs and nothing with Aero. All clean. I'm not buying it. You guys might be having other issues that are causing you to think this is a regular thing with V

You folks do notice the the original poster has not been back in a while. Maybe Panarchy really knew what the problem was, you think! You're funny dude. The guy posted his original post today (this morning at like 2am) and you think it's been a while.... HAHAHAHA!

The visual glitch when the list scrolls is a problem in explorer not WindowBlinds. The exact same corruption happens with aero. Ummm, no it doesn't. I have no problems WHATSOEVER with Aero handling this. It does it in it's sleep. I haven't seen any PCs to date with Vista on them running Aero and they range from having POS video cards to having top of the line DX10 ones. None of them exhibit this kind of issue with the scrolling on the Start Menu. N

That install of WB is not activated correctly on that machine. Im not doubting because he's so vague when it comes to "I don't know if I bought it or not", but from his system info which indicates it's activated, how can you be so sure? Just because it won't skin? I would have thought that WB would state it's not activated if it's activation engine is circumvented to force it to skin.

I have a question..... How does something like this slip by to production? It's just a simple question, that's all. Seems to have lots of holes compared to Aero in Vista. If this was XP, then hey, WB6 rocks, but this is Vista we're talking about. Do I have to wait til WB6.5 to get proper skinning in Vista now? WTH?

Do the SD guys know about this? I know someone has a way to get Neil to notice and hopefully fix this on the next patch.... in a few days?

Don't fret Zubaz, my video is 4.4 as well on my laptop and and it's not much to sneeze at. If you're running Vista and don't hit below a 4.0 on anything you're doing better the even some of the other guys out there that are buying new systems with crappy shared memory video cards in them. I've run out of fingers and toes trying to keep count on how many new systems I've seen on the shelves with Vista on them that can barely muster a 3.x for video let alone anything else. Such a shame. <br

Something else I noticed is that in Vista the Start Menu can natively "shift" itself left and right as folders expand so you can read everything. Seems in WB6.0 that this no longer functions. What are people supposed to do if there's programs a few folders deep? They won't be able to read them.

Thanks, but I don't think it's a limitation of Vista customization because even Vista without Aero changes this part of the Start Menu. I really think it was left like that because WB6 can't differentiate between Vista and XP when it comes to skinning. This is why the skins have to be updated for Vista to allow for the wider Start Menu. In WB5.5 (which was only released to be able to run skins on Vista) the Start Menu wideness in Vista was causing issues with text cutting off with all skins.

Yep, that's it.

When you're in this build and under Settings tab at top, the Titlebar Settings choice dropdowns have corrupt white background. (Make sure the WB6 window is close to the top of your screen because if not, the menu dropdowns open upwards and this problem doesn't happen in that direction.) BTW, this is under Aero, WB6 is not even skinning.

Their already associated. My point exactly.... And it's They're , not Their.

zubaz is right. i should've checked the history first before updating. The program needs to do an OS version check prior to downloading and updateing. It's not hard to have such a check put in place. You see these kinds of checks all the times in software updates... IT'S NOT THAT HARD. Screw all this 2nd grade readme crud. Build INTELLIGENT software if you want to be associated with Microsoft or it's products.

Hey, it's not me missing all this stuff. I just point it out. Think of me like that anoying media person who keeps asking all the questions no one else wants to ask and loudly points out the faults in things. Why hide mistakes. Bring them to light and let the devs learn from them. It makes for a better product in the end run... although I keep waiting for that.

Anyone else notice that when WB6 skins the Start Menu in Vista the All Programs doesn't properly change to Back when expanded and the arrow doesn't change to point to the left. Hummm, is this an overlook or another "we have to have it do this for XP backwards compat"? Please elaborate. The skin makers blame WB6 for this in WB6. Who's right?

roll back to the previous build. tonight';s build is not for vista64. i made the same mistake Classic. SDC cannot differentiate between Vista32 or 64. How lame. Why let it update if it's for the wrong version? Where's the checks for this? Scarry.