Per Pixle issue?

JRSCCivic98

Join Date 12/2005

Per Pixle issue?

Here's a weird one. Haven't had time to test it with other skins, but when I have Per Pixle enabled in WindowBlinds and use GT3 OS as a sking I don't get sounds on minimize and maximize of windows. When I turn Per Pixle off I hear the sounds. What's up with that?

Also, with Per Pixle disabled if I bring up Task Manager in front of the WB5 skin window and drag it arround it has a hard time drawing the background behind the Task Manager window. If I turn Per Pixle back on, it's fine... no tearing/slow drawing of the window contents.

windowblinds

Locked Post

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

Jafo

Join Date 03/2001

+1845

I am unsure exactly why someone would be dragging the window for so long that they need it to update or even notice that it is not.

Neil....I think it's really a case of nit-picking. The art of "Finding Fault where there IS none".

Face it guys... WB5's capabilities should have been held off until Vista came along to properly support it.

The whole idea of Windowblinds, and skinning in general is to actually do things that the original default GUI could NOT.

I am beginning to wonder exactly WHOM is not 'getting it'.

And...let's refrain from 'STFU' comments as they are discourtious, thanks....

Successfully updated karma reason!

Taskmanager not updating while it is being dragged with a per pixel skin is by design. It is not a bug.
I am unsure exactly why someone would be dragging the window for so long that they need it to update or even notice that it is not.

Neil, you and I both know that this thread was getting put to bed, but someone decided to resurect it. Anyway, you pointed out something peculiar in your second sentance. It's not just Task Manager that stops updating when clicked. And it's not the drag thing arround, it's drag it arround or just click and hold the titlebar. It generates the same pause. If you look at post #6 I included a link that just points to a simple animated gif. If you have a PerPixel skin enabled and you click the titlebar of IE that opens the link the animation will stop... if you don't have a PerPixel skin then it won't stop. While I understand where this issue is comming from and I realise like you said that it's by design... I wonder if you've thought about how it may affect certain apps that need constant updating... for instance dataloging software for automotive apps that graphs out engine diagnostics.

BTW, the first mofo that states to exclude the app from skining... THAT'S NOT THE POINT. The point is (and I was willing to put it to be until someone open this thread back up) did you think about that possibility when the shortcomming (by design) was put into WB5? Maybe I'm just thinking on a more dynamic level then anyone else using this software.

Successfully updated karma reason!

exactly! the latest builds are betas. if you're using one, you're beta testing. but if you're presently using a beta build, you voluntarily downloaded and installed it. if you aren't happy with the latest beta build, roll back to the 'official' release of wb5

Thanks for playing, but even the original release of WB5 has this issue. Wana give it another try?

Successfully updated karma reason!

Sign Up or Login and this ad disappears!
There are many great features available to you once you register. Sign Up for a free account and browse the forums without ads.

Jafo

Join Date 03/2001

+1845

I wonder if you've thought about how it may affect certain apps that need constant updating... for instance dataloging software for automotive apps that graphs out engine diagnostics.

I think you'll find its a screen-drawing pause...not a data-logging one.

There's a difference.

As for 'being put to bed', the last logged input from either JRSCCivic98 and/or Neil Banfield prior to that reference was 20060307 16.29. 'Resurrection' was 86 minutes later.

Hardly extracted from the annals of time....

If you wish it to just 'go away'...it can. Just say the word.

Successfully updated karma reason!

freebird dug is up (post 17)... it was 4 days old and no posts at that point... (I think I'm starting to see why no one here seems to be as through in finding little glitches with the software. Attention to detail... you're missing the obvious even on a simple thing like this. And while it wasn't very old, it was starting to move to the bottom of the list. Point is, we knew where we stood on the issue.) We had seen where the issues were. Also, yes it is just a screen drawing issue and not a datalogging one per say... but it is still an issue. I'm glad we all finally agree on that one. I know from Neil that this is by design, but I think it's a poor design... that's all. I'm looking forward to a possible redesign in this aspect in the near future. Maybe it'll happen or maybe it won't.

Successfully updated karma reason!

Jafo

Join Date 03/2001

+1845

(I think I'm starting to see why no one here seems to be as through in finding little glitches with the software. Attention to detail...

That'll be "thorough", then...if it's detail you want..... Spell checker

So...if someone else comments on a thread it is 'digging it up', but if you personally respond it's what, exactly?

Inconsequential?

Also...pedantry to the fore....I said 'screen drawing pause', not 'screen drawing issue'.

It is ONLY an 'issue' to you....

Successfully updated karma reason!

Thanks for playing, but even the original release of WB5 has this issue. Wana give it another try?

actually, i couldn't care less about your "per pixle" (sic) issues. i spoke in regards to your moaning about being a "beta tester". rolling back to the official wb5 release eliminates the "beta tester" nomiker.

Successfully updated karma reason!

So...if someone else comments on a thread it is 'digging it up', but if you personally respond it's what, exactly?

I didn't dig it up, I was willing to let it go away. The other laptop thread that I have was one I kept bringing up so that Neil would stay on top of it and do his testing like I asked him to. If you go back and read the last few posts you'd see that there's finally another user with the same kind of laptop that I have that's experiencing the same thing. Get off your high horse... it seems that if the major players here don't think an issue is a problem then it doesn't exist. This is still a democratic country isn't it?... or have the Nazis already invaded and taken it over? Anyway, just freaking delete this thread or something... seems to me that no one is interested in fixing the SHORTCOMMINGS of WB5, so why bother...

rolling back to the official wb5 release eliminates the "beta tester" nomiker.

Come back to earth... any version of WB5 is beta testing. Right now there isn't a single one that's bug free and if you'd see Neil's suggestions in other threads by other people you'd see that he wants everyone to run the latest version on SDC if they are having problems with the first release. I forget exactly what one of the issues were with the initial release, but I know Neil stated to use the Beta versions on SDC instead.

Successfully updated karma reason!

From my understanding of this, it looks like a Windows problem, not a Windowblinds problem. One of the big improvements in Vista is how it doesn't have to redraw when you move a window, since it creates a 3d environment.

And not every piece of software is going to be perfect. Not every minor issue will be fixed. Not even all the major issues may be fixed. The guys on this thread have been pretty generous with their attention to you, so show some courtesy at least.

Successfully updated karma reason!

Jafo

Join Date 03/2001

+1845

it seems that if the major players here don't think an issue is a problem then it doesn't exist. This is still a democratic country isn't it?... or have the Nazis already invaded and taken it over?

I would have thought that if Neil has said this isn't a WB 'problem' then it really isn't one. Likening such responses to the 'Nazis' is pretty pathetic, not to mention unwarranted.

Successfully updated karma reason!