Notepad++ 7.7.1 Release Candidate

Meta Chuh

@chcg
i’d completely understand all reasons to eventually decline maintaining someone else’s abandoned project in addition.

this is pretty stress free, as this question would not exist, if this plugin was not a part of the current package, so anything you prefer is fine.

guy038

Hi, Don and All,

Well, Don, I did some additional tests, as my previous tests were done, whatever the plugins installed for each N++ version tested. To temporaty disable the plugins, I simply placed a # symbol, in front of the name of the different folders !
( Note that, once the tests done, for a N++ version, and moving back to the plugins folder, in explorer.exe, I just had to repeat Ctrl + Z several times to get back the normal folder names, without any #, for all the plugins, which prevented me from renaming them individually : A trick that I’ve not really noticed before ! )

So, Don, more precisely, in my previous post, I meant that, after inserting the macro, below :

        <Macro name="TEST of VIRTUAL Space flags" Ctrl="no" Alt="yes" Shift="no" Key="32">
            <Action type="0" message="2596" wParam="n" lParam="0" sParam="" />
        </Macro>

in the Shortcuts.xml file and replacing n with any value between 0 and 7 to the attribute wParam of the Scintilla message SCI_SETVIRTUALSPACEOPTIONS ( 2596 ) I tested the resulting Notepad++ behaviour, enabling / disabling each associated flag of this Scintilla message :

SCVS_RECTANGULARSELECTION ( of value 1 ), which enables virtual space behaviour when creating rectangular selections
SCVS_USERACCESSIBLE ( of value 2 ), which enables anyone to use the virtual space and to place the caret at any location beyond the end of line(s)
SCVS_NOWRAPLINESTART ( of value 4 ), which prevents left arrow movement and selection from wrapping to the previous line

And it happened that :

With the last N++ Release Candidate version 7.7.1, each flag produces the expected N++ behaviour ! Quite nice ;-))
With old versions, prior to N++ v7.6.3, and, probably, since many versions ( I even tested with N++ v6.8.1 ! ), the SCVS_NOWRAPLINESTART flag does not seem accessible and, giving the value 4, just acts as if the value 0 was typed ! However, the two other flags SCVS_NOWRAPLINESTART and SCVS_USERACCESSIBLE can be handled and produce the expected behaviour
With the four N++ versions v7.6.4, [v7.6.5], v7.6.6 and v7.7, whatever the value used, between 0 and 7, the expected behaviour do not occur and it seems that the default N++ behaviour ( SCVS_RECTANGULARSELECTION flag enabled, so value 1 ) is used, instead !

I hope, this time, that I’ve clearly described my tests and their results !

Best Regards,

guy038

donho

@Meta-Chuh said:

i’d completely understand all reasons to eventually decline maintaining someone else’s abandoned project in addition.

this is pretty stress free, as this question would not exist, if this plugin was not a part of the current package, so anything you prefer is fine.

Don’t get you @Meta-Chuh, I didn’t see his reply so far, so maybe let him reply by himself or am I missing somethings?

donho

@guy038 said:

With the last N++ Release Candidate version 7.7.1, each flag produces the expected N++ behaviour ! Quite nice ;-))

So there’s no regression regarding this point in v7.7.1. Do you confirm it?
(Let’s focus ONLY on this version please)

guy038

Hello, Don,

In my previous posts, I referred to older versions of N++ because, in the change.log file of N++ Release Candidate v7.7.1,
you said, at point 9 :

Enable Scintilla Virtual Space Option change from macro.

So I supposed you’ve made some changes in future v7.7.1 version and tried to verify if something was broken in previous versions, regarding the virtual space feature !

But rest assured, concerning the Scintilla message SCI_SETVIRTUALSPACEOPTIONS, in particular, everything works as expected and no regression occurs with this Release Candidate version ;-)) On the contrary, it’s rather an improvement ;-))

Cheers,

guy038

Jonas Andersson

Hi
A minor bug:
Open documents in both views.
Search for something so the search results window is open at the bottom.
Resize the search result window… ie. drag it up a bit.
Move mouse cursor to border that separate the documents, it will now resize even when mouse button is not clicked.

Michael Vincent

@Jonas-Andersson

oh yeah, weird. I see it too on N++ 7.7 64-bit. Clicking in either editor pane after resizing search results window before moving the mouse cursor to the border that separates documents and this does not occur. And for me, when I reproduce (both views side by side instead of one over the other) it only resizes to the right, not the left.

It seems the cursor type is still set to resize mode and not cleared to regular edit mode after resizing the search results window.

Notepad++ v7.7 (64-bit)
Build time : May 19 2019 - 13:05:35
Path : C:\usr\bin\npp\notepad++.exe
Admin mode : OFF
Local Conf mode : ON
OS : Windows 10 (64-bit)
Plugins : AutoSave.dll CodeAlignmentNpp.dll ColumnTools.dll ComparePlugin.dll DSpellCheck.dll Explorer.dll GitSCM.dll HexEditor.dll JSMinNPP.dll MarkdownViewerPlusPlus.dll NppConsole.dll NppExec.dll NppExport.dll NppFTP.dll NppMenuSearch.dll PluginManager.dll PreviewHTML.dll QuickText.dll SpeechPlugin.dll SurroundSelection.dll TagLEET.dll TagsView.dll XMLTools.dll ZoomDisabler.dll

SinghRajenM

@Jonas-Andersson , @Michael Vincent,
A PR https://github.com/notepad-plus-plus/notepad-plus-plus/pull/5554 has already been submitted which fixes this issues.

@donho , have a look at https://github.com/notepad-plus-plus/notepad-plus-plus/pull/5554

chcg

Fix for NppExport is available with https://github.com/chcg/NPP_ExportPlugin/releases/tag/0.2.9.21.

chcg

@donho Unfortunately some minutes to late for 7.7.1.

Ekopalypse

@chcg - as it is a RC it still can be added to the final version I guess.

donho

@chcg said:

@donho Unfortunately some minutes to late for 7.7.1.

Thank you for taking care of Export plugin.
In anyway, it won’t be in 7.7.1 because it’s not a critical issue.
The release procedure is very heavy (it takes time) so once RC is out and there’s no critical issue then tested RC becomes release otherwise we need another cycle to test it.

It’s in the stabilization phase so the next version won’t wait too long anyway.