-
-
Notifications
You must be signed in to change notification settings - Fork 343
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
Bug: Search and Replace dialogs become semitransparent when lose focus #1137
Comments
Super! |
Please test beta version _5.19.425.1673_develop (see beta-channel access #1129). |
In the beta version the checkbox works as expected, and the setting is correctly persisted. Should I keep this issue open until release, or when should I close it? Also, when I'm running the beta, it shows an error on startup:
The View - Toolbar - Toggle Toolbar works, and the toolbar becomes big (I've got a 4K screen) but the setting is not persisted, i.e. on the next start I see the same error message. If I keep the small toolbar size, the next run is not started with the error, i.e. only during startup there is a problem switching to the High DPI toolbar. Another strange thing is that in the ini-file Settings section one of the lines is duplicated:
Should I create separate GitHub issues for these bugs, or is there a Beta channel feedback issue? How should I report these? Sometimes issues with betas are reported separately from the issues found in released versions. |
I'm running But I confirm the duplicated lines in section: [settings] when "Indentation size = 0"
|
The error message is only displayed by the 32-bit build (which I extracted by mistake). The 64-bit build silently ignores the High DPI setting and always starts with the small toolbar. |
Hello @alexiljin, Just For Information:
PS: The fist part of the "Changes.txt" (from line 32 till +/- 128) corresponds to all the changes since the "Final Version 5.19.108.1602 (January 8, 2019)". 🤔
|
As I already said, the Toggle Toolbar switches to High DPI mode, but restarting the application reverts to the low DPI toolbar (due to this error). PS: there is no such word as "loosing". It's either "losing" (which is correct in this context) or "loosening". |
Did you try with a "Pristine" Notepad3.ini : Notepad3.zip |
With the "Pristine" ini-file the issue is not reproduced: x64 build starts with a High DPI toolbar, and remembers the last setting on restart. |
Is it because you don't have an upgrade path from |
I kind of want to preserve the settings I've accumulated in my old ini-file, and not reset everything to the "Pristine" state. |
@alexiljin : The HighDPIToolbar setting is maintained in the |
@RaiKoHoff, I've downloaded the latest Notepad3Portable_5.19.527.1731_RC.paf.exe.7z, extracted the x64 exe-file and placed it in a folder with my existing Notepad3.ini, which was upgraded to SettingsVersion=2 on the first run of the new version (I've got save settings on exit enabled). If I start the new "Notepad3 (64-bit) v5.19.527.1731 RC" with this ini-file, I get the small Toolbar.
However, on the next run I get the small toolbar again. |
@alexiljin : Better to open another issue for new stuff, since it is a complete differernt issue (see title of this issue).
this will override any other toolbar settings 😸 . |
Hello @RaiKoHoff |
Well, I've asked about it previously, but got no reply then. I've always thought that beta-release issues should be reported in a more lively channel (as there can be too many of them), while issue trackers such as this one should only contain things related to released versions, including feature requests - mostly from casual users, not beta testers. I've created issue #1256 about the stuff that still bothers me about it. |
@alexiljin : Sorry for not answering your previous question. |
The fix confirmed in Notepad3 (64-bit) v5.19.815.2595. |
Notepad3 (64-bit) v5.19.108.1602
Actual: I don't like it, and I can't find a way to disable this behavior.
Just to give you an idea of where I was looking:
All of the above failed to yield any results. Actually, I don't even know who wanted or introduced this feature, as there seems to be no discussion or announcement made about it.
Expected: the find and replace dialogs should have a checkbox enabling transparency on deactivation.
In general it would be nice if the new features were announced in the release notes, defaulted to the old behavior (as opposed to bug fixes, which should default to the new behavior), and could be discovered and enabled/disabled by the user.
BTW, great job with this project! This is my new favorite editor for single text files, e.g. for
git config core.editor
. The crucial feature is to close it with Esc.The text was updated successfully, but these errors were encountered: