Hash error on Customize Toolbar plugin
-
I am wondering if I experienced the same thing last week where I wrote “A plugin is available, Customize Toolbar, that can remove the icon from your toolbar. I think Customize Toolbar only works for 32-bit versions.”
The reason I made that comment is that I had tried to install the Customize Toolbar plugin on v6.4.6 x64 portable. From Plugins Admin I clicked [Install] it seemed to get stuck on the downloader for a while and on restarting Notepad++ the plugin had not been installed. I tried a couple of times but did not get an error pop-up. I then installed the toolbar without issues on a x32 copy of v6.4.6. That worked.
This week I tried the Customize Toolbar plugin on x64 again and it works without issues.
@spanakop, can you try again?
I checked manually and am getting a SHA-256 hash of
cb415b51d78ff7d505d5966865bbba67216a00955462db0187448b06efedd50afor a newly downloaded CustomizeToolbar_5_3_x64_UNI.zip from https://sourceforge.net/projects/npp-customize/files/latest/download which is the expected value. -
@mkupper said in Hash error on Customize Toolbar plugin:
on v6.4.6 x64 portable
There is no Notepad++ v6.4.6 (and it would have been from 2019, if it did exist between v6.4.5 and 6.5.1): I doubt that’s what you really meant.
Did you mean the most recent Notepad++ v8.6.4?
-
@PeterJones Tome zine fault :-) Yes, that should have been v8.6.4.
-
I just tried again, and I get the same result.
I’ll download it on another PC and check the hash manually to see if it’s my connection causing the problem.
-
In case it helps or if some benefit to someone in the future, I have converted CustomizeToolbar into a Visual Studio project and made tiny tweaks to get it to compile with current version of VS 2022 C++ compiler.
Maybe it is a little benefit to someone at some point in the future to keep the CustomizeToolbar Plugin going.It is posted on Github.
Unfortunately I don’t have any reputation points here, and I don’t see a place to put a link in my profile, so I don’t know how to post a link here. Maybe it would allow me to PM?
-
@Cooly0 said in Hash error on Customize Toolbar plugin:
It is posted on Github.
Unfortunately I don’t have any reputation points here, and I don’t see a place to put a link in my profile, so I don’t know how to post a link here. Maybe it would allow me to PM?
If you tell us your github user name and the repo name you used, we can piece together a URL.
(The reason new users cannot put links in posts, or in their profile, is because spammers abuse it. You now only need one more upvote to get that ability, so if someone else has upvoted before you come back, you can even just put the link directly.)
But be careful: once people know where you put it, you may find that people expect you to maintain and add new features and bugfixes (for example, fixing the problem with Notepad++ v8.6.9 and CustomizeToolbar mentioned here) – you may find yourself having adopted the plugin unintentionally. :-)
-
Those 2 upvotes did it.
Here’s the Visual Studio CustomizeToolbar Plugin Project:
https://github.com/QGtKMlLz/nppCustomizeToolbar_VS2022 -
I checked out the Visual Studio build you created and it does indeed create a DLL – I didn’t actually try the generated DLL, however.
A couple of quibbles: (a) The project was set to build the Debug x64 project, but it built that into an
x64\Releasefolder. Changing the setting to Release and rebuilding did nothing, thus it appears to not be set up to build a debug version. (b) It doesn’t build the 32-bit (x86) versions (Release or Debug) at all.I checked the source for any “malicious” additions, and there weren’t any. :-)
-
@Alan-Kilborn Yea, I couldn’t figure out how else to force default build to “Release”.
For x32, I never understood why/if anyone used x32 anymore, so I didn’t pursue it. Perhaps using 2 instances side-by-side, or…?? I’d be curious to hear.
-
@Cooly0 said in Hash error on Customize Toolbar plugin:
For x32, I never understood why/if anyone used x32 anymore
I suppose one reasonable reason would be if they had a plugin that they needed that was older and it only had a 32-bit build.
