bigmuscle

Ok, if you want to post cracked versions here, then develop aero glass yourself. Bye.

"I had it for 5 minutes while windows updates installation" // do I understand correctly that this happen only when installing window updates? or does it happen on every reboot?

I didn't mentioned it in the changelog because it was no bug itself. It was one of the restriction which came with layered windows hack. Since layered windows are not used anymore (since 0.8 when not falling into backward compatibility mode) then all restrictions shouldn't appear anymore - and it is a bit hard to name all restrictions

close animation should normally work.. errrm if you have compatible UDWM.DLL (and not on 32-bit).

And it is exactly how it works. When you have incomatible DWM version than native blur simply does not work. Also, as I said many times before, blur radius cannot be adjusted in Direct3D (and neither in native) mode. The transparency level should be always set to zero else it will place another color layer on the top of the frame which makes it almost opaque. (it should be adjusted a bit only - e.g. to 64 - if you use standard Windows 8 theme). If you want to adjust transparency level correctly than just use Windows Control panel.

Ah, thanks! Now it explains why it does not work. The secondary taskbar has different class name. Now I am interested (maybe in a stupid) thing, is it possible to have more than two displays with taskbar on each one?

Could you post registry screenshot? Maybe there is something I forgot.

They should work and I just tested them with my RP theme and it works.

Thanks anyone who sent me the files, I will provide testing version soon but don't expect it will work because I probably made some mistake And when Tusticles mentiones the themes thing, does anybody have access to Consumer/Developer preview theme? It looks similar as Release Preview with some details (such as the caption buttons looks more shiny etc.)

Again, if you want to use AeroGlass for the purpose different from testing then you should not use it now and wait for final version. Yeah, you can also patch SetTimer as Blackbird256 suggest but 1) it will break other things too and 2) if you are able to do it, then you should probably patch directly DWM and write glass yourself. It will be match better than cracking some software.

To fully finish 32-bit version, could someone pack and share for me following files from C:\Windows\System32\... dwmcore.dll, udwm.dll, themecpl.dll and shell32.dll? (32bit only!!!) Rather via PM not to corrupt license of those files. Thanks!

Just reminding to anyone whole has the same problem = windows are fully transparent without blur effect. Could you try this version to confirm that it will be fixed in next version http://leteckaposta.cz/306250185

Taskbar 1 : http://img10.imageshack.us/img10/1621/taskbar1.png Taskbar 2 : http://img543.imageshack.us/img543/5879/taskbar2.png It seems to be two different controls. Thank you. Just one small thing which I probably shoould mention before. Your images are from the list of the runnings apps which is child of the taskbar. The proper info for the taskbar can be retrieved when you move mouse to the leftest part of the taskbar. WinID should provide "No parent window" in brown text in the middle and Shell_TrayWnd for Class item. Yeah, Already reported, I will fix it soon. I am not sure about this I'm aware of this crash (callstack according to your attached file), I know why it happens but I have not able to find correct solution yet :-( As stated in changelog, it requires to have compatible DLLs and works for x64 only. I will make all 0.8 features work in 32-bit soon.

Yeah, just going to react to this. I'm not sure how the secondary taskbar works. Does explorer creates one control which is extended over both monitors or does it create two controls? Could you try WinID application and get information about both taskbars?

iTunes problem is known problem with layered Windows. Since I have not managed to get some function offsets for 32-bit version yet, it is still used there, I hope I will do it soon :-)

I don't even understand how this is possible to set this to 0x10000000 ??? Makes no sense. I don't even understand how this is possible to set this to 0x10000000 Tusticles was wrong. To enable set to 0x00000001, to disable set to 0x00000000, the key must be in HKCU, not in the HKLM. In the logical sense, 0 is to disable, 1 is to enable. In the reality sense, everything different from 0x0 makes it enabled

jb3555: thank, do you have only 32bit version? If you have possibility to test x64 - could you compare 0.8 and 0.85 (link is a page back)? Maybe I fixed it in 0.85 but I didn't compile 32-bit version - and cannot do it now because I changed some other things which does not work now.

Just the reason why some registry key exists (I think they are in EXPERIMENTAL section in Tweaker app). As I develop the application, I also study a lot of new internal things in DWM. As new things come, I try to implement new (and better) functionality which seems to be working perfectly for me. But I know that someone could have problem with this, so I add some secret registry keys. When I release new version and someone reports that something does not work in the same way as the previous version, this registry settings can be used to quickly discover whether the problem is caused by the new functionality. That's the reason for this registry keys and that's why they are not supposed to be set if everything works for you. If you enable the registry value, you simply degrade your version to previous one and thus it makes no sense to test it anymore.

Many people here provide very good testing reports and I appreciate it much (if AeroGlass would ever be shareware, I have no problem to give them free license) but some people makes me angry. Really, e.g. pengipete milliontimes wrote that he cannot test it properly without knowing the list of registry keys. I told him milliontimes that there are no registry keys to test but he still writes that he want them. I told him that the list of some possible keys (which are not supposed to be set at all) can be found in readme and he shouts that I am stupid because I told him to read some manual. I really don't know what some users think - I do this software in my free time for free and for fun (and at the beginning I didn't plan to spend so much time on this). And write to them - nobody forces to use this application, so please do not use it if you don't like it. So again, respect to all who provides really good testing reports.

Hmm, you're a bit funny. You are asking for a list of registry settings. I say that it is written in readme.txt and you start shouting that I directed you into readme file. Sorry, I will not response to your posts anymore. And what more, I will not probably release any other version - only privately to some persons. You want this, there was no glass and you will have no glass.

All supported settings can be found in readme.txt which distributed with the archive. I think we already talked about it, there are no registry keys which you need for testing, live with that. Also, there is one simple thing - if you have a question "How to adjust ...." and you cannot find an answer, then just ask yourself "How would I adjust it in Windows 7?" Also, d2d1.pdb does not have anything to do with rendering blur effect using Direct2D.

I know about this problem and I admit that it is a bit worse after removing layered windows. I'm trying to find the best solution for it but since it appears just for a split of second, it does not have the highest priority. If you don't use native blur than it looks usable (fully transparent) except of windows which appears for a while only (e.g. copy dialogs etc.). Tusticles: I don't think that SiB changes the taskbar properties if you don't explicitely change it in its settings. But I can't said it with 100% certainty :-)

It is because my AeroGlass utility does not allow to change the blur. Opacity can be set directly in Windows Control Panel (or via Colorization settings in registry).

Then why did you added NativeBlur option? Btw, could you tell me why DWM Glass is not applied correctly to taskbar with startisback installed? NativeBlur sense - It is written in changelog. Please, read it. I don't know what your problem with StartIsBack is. I don't use it. But for having taskbar correctly blurred, two things must be done - 1) blurBehindWindow must be enabled for taskbar (I guess it is what SiB does when you check "Disable transparency" and 2) accent for taskbar must be disabled (else you get the taskbar double coloured resulting in very small opacity. My utility does both things when explorer starts up, I'm not sure about SiB. This has already been written. It is not bug, it is by design and appears even in Win7. When you enable native blur, it will black. When native blur is off (by default), then it will be completely transparent until the window is completely opened. In Win7, it is transparent too but colorized - this is what I want to do for next version.

I have to work out a better way of detecting needed functions in DLL files. Now it can get broken with any windows updates. Please, do not report any bugs for NativeGlass, this will never be fixed. Value 0x10000000 is nothing, or better it is value 268435456 which has absolutely no meaning.