-
-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grand rework #105
Grand rework #105
Conversation
.NET Core 3 support depends on: |
I'm getting this error https://github.com/dotnet/core-setup/issues/6189 |
This requires you to install .NET Core 3 runtime from here https://dotnet.microsoft.com/download/thank-you/dotnet-runtime-3.0.0-windows-x64-desktop-runtime-installer Does it work if you do it? |
Installing .net core is another problem I had, and that it wouldn't hurt to be better handled in the program and in the documentation. But I'm getting that error after having installed it. |
This is still not meant for public consumption yet. I'll take a look at the issue you mentioned. |
@mirh the issue you mentioned should be fixed, you can try again, although it's still not production ready |
It woooorks \o/ I had already set |
I'll take a look |
You are right, fixed |
Yeah I've also noticed the issue with the registry, will have to probably perform this out of process, no problem. Glad you liked the UI! |
I don't know how much .net core has kept, but it should be possible to ask in-process for admin permissions... Otherwise a .reg file or a batch like this launched in the normal shell should automatically do it for the user
Anyway
|
@mirh yeah I'll get to it later, currently working on some other things. Just click "close" on that dialog for now, when you are testing. |
Ehrm, that's not a dialog. It's the crash report. |
@mirh I was talking about extended gamma range dialog |
aea186d
to
6dfb670
Compare
…set registry key value
MFW I wake the computer and nothing crashed. |
Hey, thanks a lot! I've merged this but I will keep doing more updates to master in the upcoming days, now that this is pretty stable. If you have time, please check CI builds, I really appreciate your continuous quality assurance. :) Also, if you need to reach me, my Discord is Tyrrrz#5447 |
CI build 202 / 6e28ef7 won't start for me. Tried the portable and installed version. Windows 7 x64. |
Did you download .NET Core 3 runtime from https://dotnet.microsoft.com/download/thank-you/dotnet-runtime-3.0.0-windows-x64-desktop-runtime-installer ? |
TL;DR at the bottom :) I wish I'd noticed the CI link in the readme before, I've been checking this page religiously for a month, looking forward to a new release. Grabbed the latest build as of today, hooray! (Pro tip: Don't do this at 0330 MY EYES ARE BURNING lol) I downloaded the runtime linked above, and the app failed to start. Logs show the following:
Indeed, the hostfxr.dll file is not installed in either the lightbulb or dotnet directories. According to this issue: https://github.com/dotnet/cli/issues/3907 this issue is worked around by having installed VS, so I would guess that's why it is not effecting you. Following the pre-requisites mentioned in that issue, I found myself on the following page: https://dotnet.microsoft.com/download/dotnet-core/3.0/runtime This lists two requisite downloads, the second of which is the one linked above. The first download, installed the missing DLL, and Lightbulb started. TL;DR Not sure that we need this: https://dotnet.microsoft.com/download/thank-you/dotnet-runtime-3.0.0-windows-x64-desktop-runtime-installer We DEFINITELY need this: https://dotnet.microsoft.com/download/thank-you/dotnet-runtime-3.0.0-windows-x64-installer It works now. Oooh, pretty! |
@NomDeMorte thank you for letting me know. I was under the impression that desktop runtime includes the base runtime, but I guess not. I will make sure to include these instructions when v2 is released. :) |
You're very welcome and thanks for the great work. Already enjoying my 66% brightness at night, and my altered day/night times :) I do wonder, based on the event log, if perhaps you might just be able to package the DLL with the application:
If you would like, I could try to un-install the dotnet stuff I just installed, and copy that DLL to the lightbulb directory to see if it works? (I assume it is not so easy for you to test, given that you have the full dev environment in place there).... But perhaps I am mistaken. Let me know if I can help in any way. |
I think it's just the first dependency it failed to find and there's more. There's a way to make the app self-contained so you don't have to install the runtime but I'm not a fan of that because it makes the size much higher, i.e. ~200mb. If we make sure the users know what they need to download, I think it should be fine. |
It's probably a mixture of my optimizations and .NET Core. Good news eitherway.
It didn't use to do it before either :) It's probably better to create a separate issue for that |
.NET Core runtime should hopefully be installed by the latest installer now. |
It would be even nicer if the executable alone could warn you gracefully it is missing, rather than just crashing badly |
Unfortunately that's not possible |
2.0 still isn't working for me (won't start and doesn't show any errors). No other lightbulb instance was running when attempting to run lightbulb 2.0. What I tried: It's probably a missing windows update. Edit: It was a missing update (KB2533623). |
@aure2006 can you check the Windows event log? Press Start and type "event viewer" and then go to Windows logs->Application. See if there might be something related. You would be looking for something like this: Although it might be something else |
Found the fix and added it to my previous comment. |
Great! |
LightBulb is a rather popular blue light filter but it hasn't been significantly updated in a long time.
Current version of LightBulb was designed with simplicity in mind but this design hinders adding new features that the users want. The idea is to rework LightBulb, both the back- and frontend, to make it more scalable in regards to future improvements. This is a step away from the very simplistic UI that LightBulb used to have, however the aesthetic hopefully will remain the same.
This PR will address these issues:
Closes #28
Closes #55
Closes #59
Closes #66
Closes #73
Closes #95
Closes #98
Closes #90
Due to a large amount of changes, it's likely (although not guaranteed, will need to be tested) that it will address these issues:
Maybe affects #102
Maybe affects #42
Maybe affects #32
Maybe affects #29
Maybe affects #99