-
Notifications
You must be signed in to change notification settings - Fork 5
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
a kritical problem with ngt's context menu registrations #7
Comments
GreetingsHello. The following are the reasons why projects are out of date. Unexperience InstallationSince I have not much experience and/or knowledge with the NSIS installation maker, that problem could have occured. Maybe me or someone can learn the NSIS codebase and make one installer for NGT. I cannot sure I may do that, read below. Switching To NVGTThe fact that I am now focusing on the ability of producing my own include scripts at NVGT language which has recently been published into the public interestry, the include scripts for NGT as well as BGT has been out of date. Even though I am switching to NVGT, include scripts aren't yet published do to my sickness, read below. My Health RecoveryAlthough I might reupdate them as soon as possible, I cannot do for now, do to the fact my health recovery. I'm sick since 3 days of this writing, and I have significant out of date at all over in my projects. ConclusionWell, that's all I have to say. I will still this issue as open until it resolves. |
hello. I've installed ngt, and then, when I pressed application on all my files which had .ngt extention, The open o option has been renamed to open with ngt, and when I uninstalled ngt, and then I pressed application on my files which had .ngt extention on them, the Open o option was gon from them, so now if i press application on any of my files with any extention such as .badBoy, .BadGirl, I have the open o option, but for .ngt files I don't have this option. What is wrong with ngt's registration of changing context menus up on uninstalation?
The text was updated successfully, but these errors were encountered: