@Murray-Sobol-1 said in Idea of a new installation routine:

@PeterJones said in Idea of a new installation routine:

No one should ever download a 32bit installer for modern OS. For any app. (Modern OS don’t come in 32-bit versions anymore, so I don’t understand why apps still bother distributing the 32-bit versions)

I agree with the above statement, however when I ask for an update by clicking Downloads I see this section:
Download 32-bit x86
Installer | GPG Signature
Portable (zip) | GPG Signature
Portable (7z) | GPG Signature
Mini-portable (7z) | GPG Signature

Why is this even being distributed anymore??

Because my statement was just my opinion, and not everyone agrees with it. Because there are some people who mistakenly think they need a 32-bit even though they have a 64-bit OS. And there are some people who have some unmaintained plugin that only comes in 32-bit (*). And because the developer has never decided to cut off those poor, unfortunate souls.

(*: aside: anytime I come across someone like that, I do a bit of research to help them find an alternative, or find someone who has done an unofficial recompile of the plugin for 64-bit. there are very few public plugins that have no 64-bit version and no alternative)

But that’s why we lobbied to put the 32-bit below the 64-bit, so the 64-bit gets the prominence it deserves – and why I rejoiced when it happened. Someone downloading N++ for the first time will see the 64-bit first, and will likely download that. Someone updating N++ should use the menu or auto-update, and never have to go back to the website.

@Carlos-Sánchez said in [New plugin] Smart Math:

I’m a bit lazy and haven’t got a clue

I can’t solve the first part, but for the clue:

it’s just a PR to the nppPluginList project. Since you’re working in GitHub already, I assume you know how to do the PR fork the nppPluginList repo, create your own branch in that branch, edit pl.x64.json to link to the 64-bit version, and pl.x86.json to link to the 32-bit version the id required in the JSON is just the SHA256 hash, which GitHub provides for you:
fd4a838f-9724-477d-b755-24836141dc88-image.png once you have edited both files in your branch, submit the PR from that branch

@PeterJones said in Is There a Way to Prevent Pasted Text from Spreading Out with Rows of Spaces?:

Should I delete python27.dll from the PythonScript folder? This time, I copied and pasted and followed the prompt to replace the existing files. Last time, I deleted everything before copying over the extracted files. Is that why it didn’t work?

How could it be there? You literally said last time that the directory didn’t exist. If the directory didn’t exist, python27.dll cannot be in it already. If it did exist, you should have said it did exist.

It didn’t exist at that time. I reinstalled 2.1 via Plugins Admin to restore the Python folder and pasted the extracted contents into it. Oh, and should I delete python27.dll?

Is it possible for the script to work without first pasting the IMDB text into the Find search box?

The script has absolutely nothing to do with the Find box. I have no clue how you got the impression that it requires that.

I had the idea before my OP, when I posted about using the Find box, DuckDuckGo, and Everything.

I don’t see anywhere in the FAQ how to apply an icon to the script.

Also, what icon would I use? Is there a way to create, or import one if none are available? BTW, I have the Old Large Legacy Icons installed, and there aren’t any unused ones available under Plugins > Customize Toolbar

@Guido-Thelen said in C# Plugin for ARM64:

DNNE (Dot-Net Native Exports) is a modern NuGet package that generates a native C wrapper DLL around your .NET 8 assembly. It uses [UnmanagedCallersOnly] attributes to define exports and supports ARM64 natively.

I assume you mean this?

I tried it, and quickly ran into the limitation that custom types require user-defined C-language equivalents, which are passed to the code generator as strings of C code(!)

So, for example, to export the setInfo function from a plugin, you would provide a definition of the C++ template’s NppData structure that compiles to the C99 standard. (The generator can emit C or Rust, but not C++, in the interest of portability, I guess.) Then you annotate the method with your type definition code, and apply the C type specifier to the corresponding C# type:

[UnmanagedCallersOnly] [DNNE.C99DeclCode("#include <windows.h>\r\nstruct NppData { HWND _nppHandle, _scintillaMainHandle, _scintillaSecondHandle; };")] public static void setInfo([DNNE.C99Type("struct NppData")]NppData theData) { // use theData ... }

This would be quite fragile against API changes, unless you can produce the code strings automatically from the Notepad++ headers.

It’s much easier to install a template package and target ARM64 with Native AOT. You can even start a project in Visual Studio:

vs.npp.dotnet.templates.start.screen.png