@Coises said in Styling Speed tied to Visible Area:

Have you checked whether setting different options for SCI_SETIDLESTYLING makes any difference?

I tested them right now, and they make no difference. They seem to be more tied to a direct lexer implementation, as they control the threads for styling.

@Thomas-Knoefel Just a short update on my achievements. I managed to compile everything using the original N++ sources. However, upon further investigation, I realized that if I wanted to use the Lexer, I would need to adapt a lot of code to fit into the plugins framework.
I decided to run some tests by setting the styles without a Lexer. Remarkably, I found that using Styles instead of Indicatorstyles (which I initially used for my first test) was much faster than expected.
Surprisingly, the speed almost matches that of a Lexer (even if it is 3 times slower, it still offers good usability for that purpose).But i think i will probably leave the N++ Source Code next to the Plugin to have a better updated in future for some other files.

One more idea that requires help of someone familiar with HTML.
It would be great to add a search index (ability to search for a given word) to the online NppExec Manual.
I’ve created the corresponding issue on github, please feel free to comment right there:
https://github.com/d0vgan/nppexec/issues/80

Every menu item should have a Boolean property similar to the _init2Check member of the FuncItem interface type. Setting this to true makes the checkmark appear.

Assuming your plugin initializes its menu items in a constructor, the ::setInfo function is where you would assign the restored state to each item’s _init2Check member, or whatever your implementation calls it. One of my own plugins does exactly that by reading values from an *.ini file.

::setInfo is called by N++ before ::getFuncsArray, and long before the toolbar gets drawn. Up to now you’ve been calling a window procedure, but your menu items need to be created and configured even before there is any window to receive messages.

@David-Slipper ,

Notepad++ is a Windows application.

Ones that are easily accessible on Ubuntu are running in a Wine or similar environment, and are unofficial distributions.

So if you have that environment, you may be able to manually download the ARM version that @terry-r mentioned and get it to run. And maybe whoever supplies the easy-to-install bundle for Ubuntu might choose to eventually distribute one for ARM Ubuntu as well.

But Notepad++ developers do not support it running on any non-Windows environment, and do not and will not supply bundles for non-Windows environments

@PeterJones said in Debugging Npp .exe without a debugger (beginner):

I assumed @Victorel-Petrovich wouldn’t mind it being moved

True

@rdipardo @Alan-Kilborn it looks like there is a fix now available. https://community.notepad-plus-plus.org/post/88610

Thanks for all your feedback!

@rdipardo :

BinaryKits.Zpl.Viewer as a project reference and building it yourself.

sure, thanks for the suggestion. will try that way…

@909369409 said in Cannot run NppPlugindemo in Npp8.5.4 X64:

C:\Program Files\Notepad++\plugins\Demo\NppPluginDemo.dll

You need to rename the directory under plugins like C:\Program Files\Notepad++\plugins\NppPluginDemo\NppPluginDemo.dll

or rename the plugin.dll to demo.dll like C:\Program Files\Notepad++\plugins\Demo\demo.dll

@dinkumoil thanks, I will try it.

@Ekopalypse , @Alan-Kilborn , and others,

I think the difference is that in the situation called, there are two layers: there’s the NppExec script, which is being called by the shortcut; then the NppExec is using SendMessage to activate the PythonScript menu from a “click the menu equivalent”.

So while the shortcut is associated with the NppExec script, it’s keys are still “active” when the menu is “clicked”, so the PS check of “am I being Ctrl+Clicked” sees the Ctrl from the NppExec shortcut and the click from the NppExec SendMessage.

Whereas, when you just run a PythonScript with a keyboard shortcut, it isn’t also getting the “clicked” attribute.

At least, that’s what I’ve gathered from the evidence given in this dicsussion; I could easily be wrong.

@rdipardo Oh wow that worked great!

Really appreciate the time you guys took to help me, thanks!

@Vitalii-Dovgan If you preserve a file’s modified time stamp then Notepad++ does not notice it has changed. Thus it’s possible to sneak in and make changes without triggering the pop-up.

Of course, that also means Notepad++'s in-memory copy of an open file would be out of sync with with what’s on disk. If you do File / Reload from Disk then Notepad++ will pick up the new file contents. Reload from Disk is also available in the right click menu for the file’s tab.

@pnedev Sorry for necroposting, but why no one said magic words “Group policies”? Chromium (and Chrome ofc) extensively uses this feature. Yes, in order to use this feature Notepad++ should provide administrative templates, but it is not that hard.

@Alexander-Verbitsky Congratulations!

@Vitalii-Dovgan said in Auto paste the selected text automatically into One File:

I’ve found the idea of the Clipboard Monitor to be interesting enough to experiment with and to include it into NppExec Manual.

You are amazing! I simply could not use Notepad++ without NppExec.

Cheers.

@rdipardo said in New version of HTML Tag:

By urgent request,

My “urgent request” and thank you for promptly adding this feature. Certainly not expected to be this quick, but you are a very talented and dedicated developer and I do appreciate your commitment to Notepad++ and supporting the plugin ecosystem.

This will certainly make my workflow (currently involves creating / editing XML schemas and docs) much easier as the tags update and change in the flux of this development period and auto-selecting the matching tags (sometimes far away in the document and nested) for renaming saves so much manual time.

Cheers.

@Michael-Vincent said in Catching the SCN_UPDATEUI event in Plugin:

Why not just do it the “plugin recommended way” (as per the Notepad++ example plugin):

Thxs, Michael. Your suggestion was exactly what I needed. It was simpler than I initially thought, yet I spent hours figuring it out.

I couldn’t get the plugin to do anything, for either Python or C++. :-(

I make a selection, then press the toolbar button and nothing happens.

I notice the plug hijacks Ctrl+q. I’m a believer that plugins should never assign keycombos.