Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Blonk

Member
  • Content Count

    24
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Blonk

  1. I use an addon for firefox called "glassmyfox" which works very well. The developer has one for thunderbird too called "glassmybird" which I haven't tried but might be worth a try. https://addons.thunderbird.net/en-us/thunderbird/addon/glassmybird/
  2. From a post by @412070391 (which was scrubbed with the msfn server crash):
  3. Just my 2 cents, part of a developer's interest is the fun and reward of their work. I have noticed for other useful projects in the past, too much negativity (nagging, repeating the same complaints, etc) rather than taking the time to thank the developer for their work often leads to the developer (understandably) losing interest. For the development and updates of AeroGlass, I doubt Bigmuscle has any help and he probably has other commitments too, so we should be grateful that he is still working on it despite MS's updates constantly breaking it. Also, I very much doubt the donations come close to paying for his work, so it is still to a large extent voluntary work on his part. The April update was released on the very last day of April, only 2 1/2 months ago (not 4 which seems to be quoted regularly here). Bigmuscle has taken longer than this in the past, at a time when more people were posting on the forum and yet fewer of them complaining. So perhaps we can return to the OP topic and thank Bigmuscle for his continued work and for his latest release, no matter when it does come out.
  4. I think the confusion was because the pop-up boxes are to gather info that is helpful to the developer. You still need to manually copy and paste the details (if asked for when dealing with a particular issue). None of the pop-ups nor Aeroglass in general will forward any information behind your back.
  5. The console is built into the debug versions in case you need to give detailed feedback. This will go away in the final release, in the mean time you can either minimise it or move it to another desktop. Closing it as you have found will just restart dwm and bring it back.
  6. The experimental build was last updated on Jun 17, so is clearly still in active development. Many thanks to BigMuscle.
  7. You using #506 Yes, I downloaded 506.7z from "Beta #506 (32bit+64bit) (Updated on 17th November 2015)" on the TH2 page. I tried downloading it again to be sure, and I have rebooted each time. The datestamp on the DWMGlassxx.dll files are both Nov 17th in my C:\AeroGlass folder. Edit: I have Windows 10 Pro build 10586 x64
  8. Still getting the watermark on vlc fullscreen here.
  9. With build 333 is the watermark appearing on fullscreen apps (tested on vlc full screen) an intentional new feature?
  10. There is a link on page 2 of this thread (post #40)
  11. Many thanks. I'm using build 333 (which I think is for 10525) - if the same-colour isn't a new feature of that build then I'm guessing this is a windows 10 change (probably the introduction-of-colour feature there). Apart from that, 333 seems to be working good for now with 10586 (apart from the unreleased symbols issue others are having which wont be fixed till they are released)
  12. With previous versions win10 + aeroglass had a different colour for the titlebars to the taskbar. With the latest TH2 version of aeroglass and the recent release build 10586 they are now the same colour. Is this win10 or aeroglass that has changed this and is there a workaround?
  13. One possibility would be the caption glow effect which doesn't seem to work on the win 10 default or the win 10 based themes so far
  14. Good question. I have not checked the difference between frame and accent color yet, but I may inspect it for the upcoming release. Hopefully it will be implemented as an option rather than a change, some of us like the two different colors
  15. Is there a version of this or the default black one which includes caption glow?
  16. Currently only a 64-bit version of modernframe.dll has been implemented/tested, BM may or may not add support for 32-bit at a later stage but for now this will only work on 64-bit systems There will be some new folders where the symbols have been downloaded in C:\symbols You need to copy or move these folders to your aeroglass installation, on my system the destination folder is c:\aeroglass\symbols. Once you have copied them across, reboot and the error should go away.
  17. I am on 10240 so my symbols wouldn't help Has anyone else had any success updating symbols (either directly from winaero or by another means) for build 10532?
  18. I had this error first of all, reinstalling debugging tools seemed to fix it. It looks like from NoelC's post that aeroglass is trying to update the symbols but the firewall is preventing it so it might be worth turning off the firewall for a very short period whilst letting aeroglass do the update, or reconfiguring the firewall to allow aeroglass. I haven't tried it but endbase also suggested resintalling aeroglass which also seemed to fix it.
  19. This seems to have started after the latest updates (one of KB3081448, KB3081449, KB3081452) which has likely updated the dwm files. Either I am doing something wrong with symchk (if so if anyone has any advice on downloading symbols that would be great) or the newer symbols aren't available yet on the symbol server. So far aeroglass still seems to be working ok for me despite the message. EDIT: Ok I managed to get this working by reinstalling "Debugging Tools for Windows", opening a command prompt, navigating to the debugging tools folder ("C:\Program Files\Debugging Tools for Windows (x64)" in my case) and using: symchk c:\windows\system32\dwmcore.dll /s SRV*c:\symbols\*http://msdl.microsoft.com/download/symbols symchk c:\windows\system32\udwm.dll /s SRV*c:\symbols\*http://msdl.microsoft.com/download/symbols symchk c:\windows\system32\dwm.exe /s SRV*c:\symbols\*http://msdl.microsoft.com/download/symbols (dwm.exe isn't specified on BM's guide page so possibly isn't needed, also you will probably need to hover over the msdl link part above and edit your command line as the forum seems to shorten the urls with ellipses, or clicking on "Quote" as though you were going to reply to this post and getting the full lines from the reply area works too) I copied the symbols folders from c:\symbols to the symbols folder under the aeroglass installation and rebooted (just clicking on "retry" in the warning dialog didn't work for me), and the warning message didn't come back.
  20. How can I apply the caption glow effect? Using AeroGlassGui, I have tried each of the available settings, the only one that appears to have any effect is "Use theme settings" which pushes the text along the titlebar according to the value but still has no glow effect. I am using Win 10 build 10240 and have tried the stock atlas (unticking theme atlas image) and the atlas from post#189 (which is the look I like and is the only one that seems to have a compatible png). Would I need an edited theme, eg an altered version of the one in post#189? I had previously applied the "colored title bars" theme from winaero before installing aeroglass which is the only thing I can think that might have broken it if it is broken. Also some atlases here have a blue highlight when hovering over the minimize and maximize buttons which match the red one over the close button, how easy would it be to add that to the theme in post#189?
  21. OK many thanks. Like you said it is still experimental, it is amazing BM has got it to work as well as it already does in the short time since Win10's release. It would seem you can make bringing up the taskbar from the top more reliable by closing the ApplicationFrameHost window before opening an app you want to run full screen (which restarts the frame host window). Many thanks again for your help.
  22. Ooops my bad, I had tried the ctrl-maximise with the dll disabled as I had assumed the shortcut would work regardless (I thought there may be a generic Win 10 shortcut). I re-enabled the dll (downloaded from http://www.glass8.eu/win_future.html so the latest as of Aug 7) and ctrl-maximise now works, many thanks. Since the title bar and therefore the maximise button cannot be reached once the modern app is fullscreen with the dll enabled, is there a shortcut to "un-fullscreen" the app again without having to close it and reopen it?
  23. Hi, many thanks for the quick reply! Unfortunately this isn't working for me, holding the control key and clicking the maximize button seems to be doing the same thing as clicking the maximize button on its own (leaving the title bar and taskbar still visible). Is there another way or am I doing something wrong with the keys? Sure hold down the control key while you click the maximize button.
  24. Since the fullscreen button is not yet implemented in the titlebar for modern/universal apps with this installed (which might be needed for some games or video players), is there a shortcut key or other way that an app can go fullscreen in Windows 10 without the need for this button?
×
×
  • Create New...