Jump to content

ORelio

Member
  • Posts

    169
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by ORelio

  1. Didn't noticed this lack of glow. To be more precise, the tweaker copies the DLL from its folder to C:\Windows before loading it in order to allow to safely delete or move the GUI files and ensure that the full path of the required DLL does not contain any spaces (Can't put spaces in AppInit_DLLs paths even with quotation marks). But as it's loaded into memory it may be impossible to overwrite it with the new version so disabling Glass & rebooting before applying the new version should be the right method for upgrading the file. EDIT: By the way, bigmuscle, what are the bugs / things that need to be fixed for the final version?
  2. There's nothing special to do with this except clicking OK. I assume that bigmuscle intends to release the final version as a shareware and thus added "DEMO" messages in the beta to avoid releasing an almost stable version for free and encourage people buying the final version. I disapprove but that's bigmuscle's software, he has the right to do what he wants with it and I'm tired of struggling with those nag dialogs, won't make further attempts to hide them before the final version of Aero Glass for Win8.
  3. Unless bigmuscle makes significant changes, the GUI should be compatible with any upcoming version : Simply replace the dlls that come with it with the new ones and it should be allright. To properly delete the loaded DLL it would be necesary to disable Glass (using the GUI for example), then reboot the computer, and then enable the new version by running the tweaker with the new dll. This method should work. Glad to hear that my tool is useful for you. (For further feedback aboud the GUI, please consider posting in the asociated thread, see link in my signature )
  4. I learned about AppInit_DLL while making v1.2 and know that it's loaded in every process but as dwm draws the windows, killing & restarting it causes the new settings to take effect, and that's what is the intended result. Restarting other processes is not needed, in fact: the taskbar color is also affected without having to restart explorer.exe (don't know why, but it works ) Of course deleting the DLL often fails because it's still loaded in a process, but the GUI tries to delete it and if the access is denied the error is ignored.
  5. Version 1.2.1 is out ! Added color picker and rounded corners option. Added your updated install program to the first post, DosProbie : )
  6. Never noticed that there is a different registry key for blur in Direct3D mode. Which registry key is the correct one for Direct3D mode ? I'll change the GUI to write the blur value in both of them.
  7. I simply kill dwm.exe process, which makes it restart and thus reload the DLL ... as simple as that. When activating Glass, my GUI place the correct DLL (DWMGlass32 or DWMGlass64) in C:\Windows, register it as AppInit_DLL and kill dwm.exe to instantly load the DLL. And when disabling Aero, it does practicaly the same : unregister the DLL, kill dwm to unload it, and delete the file from C:\Windows. Why looking for a complex method when a simple process killing trick does the magic for you ?
  8. How can I read the active window colour ? (I'll add a checkbox for rounded corners.)
  9. @MrGRIM : Rounded corners does not work well yet, see screenshot here @Pengipete : Nice idea, I'll try to do so (never tried to set this registry value)
  10. Tried to enable rounded corners, it works well except that a rectangle is still drawn around the windows ^^ (I prefer non-rounded windows, but I was just trying, to see if it works)
  11. Just updated the GUI, it creates registry keys for you if you have some trouble creating them yourself:
  12. Here is the update for Aero Glass v0.7 BETA 1 from Big Muscle : [*] Updated command-line usage & fit the new preview/beta [+] AGTweaker is now fully portable and no C:\DWM folder is created [+] Supports both 32 and 64 bits systems as the new preview is 32-bits ready [+] DWMGlass.dll is automatically installed / removed in C:\Windows when enabling / disabling Areo [-] Removed debug log cleaning as the new beta does not generate debug logs [-] Removed notification area icon (no more needed)
  13. Works perfecly for me, note that I'm still using Direct2D instead of Direct3D because of the way windows are colored in Direct3D. @Ex_Brit: Take a look at
  14. OK so here is the update for preview 6! [*] Updated to fit the new preview [*] Updated dialog skipping method to fit the new popups [+] AGTweaker stays in notification area and automaticaly closes "Preview Only!!!" popups [+] Supports the new startup method provided by BigMuscle [+] Automatically detects wrong registry values for blur and opacity [+] Automatically detects which drive is the system drive [-] Removed settings that are no more needed [-] Removed Interop DLL (no more needed) ... Right after posting this update for preview 6 I saw the new 0.7 preview/beta so ... let's go for another update
  15. Ok, I'll add a method for selecting the correct drive in the next release I do not have much time right now but I have not forgotten to do the update for 0.6!
  16. An update is coming soon, don't worry Try lowering color intensity for window borders in Personalization panel.
  17. Had the same issue with direct3D mode, it can be solved by lowering color intensity in Personnalization pannel or switching back to Direct2D
  18. Same for me, I have random freezes with 0.4 & 0.5 so I stayed with preview 3 ... I'll try 0.6 as soon as I have some free time ! (Also ... I don't see the point of putting a nag screen every hour unless ... are you plannig to provide the final version as a shareware ? )
  19. My pleasure, if you have any further question don't hesitate
  20. As detailed here it should be a DWORD (32-bit) value, you may have chosen another type:
  21. Yeah, that's from Radiant Registry paths are detailed here:
  22. Ah, lol! Your registry value for Transparency or Opacity is wrong, it should be between 0 and 255, so starting the app with a registry value of 304 crash it. I'll fix that in the next release. While waiting, delete or modify the registry keys with a wrong value. Thanks for the full crash report
  23. Hum, Okay but with the content of the "Details" Box it would be better... Could you copy and paste the contents of the "Details" box? ^^"
×
×
  • Create New...