Jump to content

Chris123NT

Member
  • Posts

    51
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Chris123NT

  1. Wonder if this will work on the freshly released 10525 Only one way to find out lol.
  2. Had a dwm crash earlier, here's the event log data from it: Faulting application name: dwm.exe, version: 10.0.10240.16384, time stamp: 0x559f3907Faulting module name: KERNELBASE.dll, version: 10.0.10240.16384, time stamp: 0x559f38c3Exception code: 0xe0464645Fault offset: 0x000000000002a1c8Faulting process id: 0x764Faulting application start time: 0x01d0d7011377511aFaulting application path: C:\Windows\system32\dwm.exeFaulting module path: C:\Windows\system32\KERNELBASE.dllReport Id: 682b25f6-1fcb-440d-87e7-4771f05948cbFaulting package full name: Faulting package-relative application ID:
  3. This build is awesome so far. Question about the provided atlas, what is required to make it "borderless", as in no artificial borders on the sides and bottom.
  4. bigmuscle, why don't you release the current "experimental" build? According to my experience (and I believe, by the other testers here experience) this build is stable enough and working fine on the released Windows 10. I know you are "perfectionist" but it's simple not possible to release 100% bug- or issue-free builds. And of course release will stop some people negative emotions and feedback. I know that you don't care however... Some people (including me) donated you (and some - a few times), they are like your app and feel uncomfortable without transparent captions (yes, sir, it is! sounds crazy but it's a fact). Yeah you are big boss here but could you please show a little appreciation to the people who loves what you do? Thank you very much, WBR, Sergey There's still bugs that I imagine he wants to fix, for example monitors left of primary have negative pixel position coordinates which is causing issues with the dev build.
  5. Not for users that don't know anything deeper than how to go to the internet.If I tell you stuff in German language you have to know at least that I'm talking German so you can use a translator to understand me. Alter, war das nicht klar, dass ich Deutsch spreche? (means "Dude, wasn't it obvious that I'm talking German?") If you just know "Deutsch" is "German", it can't be obvious in any way. He clearly states it's a debug version, it's not his problem if people don't know how to read before they click download. Now, can we get back to doing some constructive testing and help bigmuscle make the production version be the best it can be?
  6. Then setting the left most screen to primary would fix the issue, lending to support your theory about a possible variable issue with assumptions of positive screen coordinates.
  7. Yeah, provide your debug.log. But I see it as difficult to catch because it seems that multiple monitors virtualization does not work in Win10 with VMWare. In Win8, I can simulate any number of monitors but it displays error message "Cannot save displays settings" in Win10. Hm, I just tried making Win 10 full screen in VMware then choosing a view that puts it across all 3 monitors here, and it does work across the 3 monitors for me. Kind of slow - really slow actually - in making the transition, but after 15 seconds or so the "device recognized" sound plays and all 3 monitors are controlled by Win 10. I can reproduce the issue also I think... If I hover my mouse over controls just below the title bar on my left monitor (Windows thinks that's monitor number 2 in my case) I can cause some minor visual glitches in the title bars. To be honest they're so subtle I wouldn't have noticed them. I don't seem to be able to make it happen on the central monitor or right monitor, just the left one. Here's the whole screen grab: http://Noel.ProDigitalSoftware.com/ForumPosts/Win10/10240/ScreenGrab_08_04_2015_061706.png The following log covers the time where I booted the VM into windowed mode at 1920 x 1200, then switched to full screen (2560 x 1600) then went to 3 monitor mode (4960 x 1600). I don't seem to be able to log off/on in the VM and remain in 3 monitor mode (VMware limitation?), so I can't test a fresh startup at the final resolution. No messages at all are logged at the time the glitches show. -Noel Noel that's the exact thing I see, and surprise it's only my left most screen doing it. Center and right are always fine. I'll post my debug.log when I get home and repro the issue again.
  8. It depends on the problems/bugs/feature requests which appear in next 1-2 weeks. Since I don't use W10 myself, I cannot test it much. There are still some bugs which I need to address but also some things which I am not able to implement correctly on Windows 10 RTM (FrameMargin, different opacity for inactive frames etc.). There is definitely an issue with triple monitor setups. Everything is just fine on screens 1 and 2, but everything displays artifacts on screen 3 in glass enabled areas when hovering over caption buttons etc... ​ If you need any debug info from me to diagnose the issue let me know.
  9. Unfortunately I just had to disable glass for the time being. For some weird reason it is displaying corruption on my 3rd screen when hovering over glass enabled areas. Screen 1 and 2 are fine though which is rather odd. Anything you want me to try bigmuscle?
  10. .. Why do you care? It's my issue, if I want to something to my computer, that's on me. This build is for testing only, you want to help bigmuscle or what? Not my job :^) I appreciate the work on the hook Muscle, but sometimes you and Noel act kind of dick-ish. So wait, giving you early access to a dev build of a program that does something you want so you can try it out and offer feedback is being dickish? Wow.
  11. Had a weird issue just now, was RDPed in from work and everything was great, I just got home and logged into the machine and everything was corrupt on screen and DWM elements were not displaying correctly, a simple reset of dwm.exe fixed it but here's my debug.log if it helps track down the cause of the issue. debug.txt
  12. It's ugly because it looks like you have a screwed up atlas installed.
  13. Installed and working well here, only thing I see is even with a donation key installed I still see the watermark but I'm assuming that's because this is a dev version. Regardless of that it's been very smooth on my 3 screen desktop so far, good job!
  14. Can't wait for the official release for Windows 10 RTM, this is going to be a must have addon for me for Windows 10. BTW bigmuscle I can confirm that 10240 IS RTM, so you can proceed full throttle with your development of this epic program
  15. I have glass enabled on battery on my laptop and notice ZERO difference in battery consumption vs glass being disabled. Don't believe the MS party line about why they gutted glass from the Win 8 UI, it had nothing to do with power usage, but everything to do with tablets having crap GPU's.
  16. Color intensity is at minimum. Changing that will only bring color to the frames, but does not change the transparency. I have a dual monitor setup running on an AMD R7 200 series with driver catalyst 13.12 As I move the windows up \ down - it looks like there is a background image with diagonal lines behind the window frame. The diagonal lines start at the top of the screen and go right at the bottom. These lines or shadows appear to be fixed - they do not move and dragging the windows around will just reveal the position of these lines. Uhh, glass might think you're on battery for some reason. HKLM\Software\Microsoft\Windows\DWM Create a DWORD called DisableGlassOnBattery and set the value to 0 and restart DWM.
  17. Well hopefully he has a new website up soon. Would have been nice to have one up before berlios shut down but maybe there was something that came up which prevented this. I'm sure it will be resolved soon enough.
  18. I did a post on my blog about this a few weeks ago, describes how to do everything you just asked about: http://www.chris123nt.com/2014/04/10/how-to-get-aero-glass-back-in-windows-8-1/ The symbols part isn't needed anymore since bigmuscle released a hardcoded release for update 1.
  19. The chances of your PC being hacked by glass are much less than with any other app that does things under the hood. You should see the shit that stardock apps do. You have a better chance of having aliens bust down your door and poke you with anal probes within the next 5 minutes.
  20. Can you clarify (when you get a chance) does your hardware binding algorithm look at the serial number of the HD(s) or a piece of information that can potentially change simply by re-formatting or re-partitioning said physical drive?
  21. The only way your donation key will stop working is if you changed the hardware it is bound to. Either your hard drive or your CPU.
  22. I took your fixed up version of win8rp and changed the spinning donut to the Windows 8 style spinning donut EDIT: fixed the right inactive border which I accidentally damaged when pasting in the new donut. Awesome work, it looks great!
×
×
  • Create New...