editor.getTextRange() not present in 3.0.23 release

[alankilborn]

I can't tell if this is intentional or not, as the "What's Changed" section is hard to read from a user perspective because it is auto-generated.

I tried: PythonScript_Full_3.0.23.0_x64.zip.

[chcg]

@alankilborn Intentionally, updated release notes:

update to N++ 8.8.2 and removal of corresponding methods from pythonscript which are commented out from N++ scintilla interface:

deprecated by N++ 2GB+ support via new scintilla interfaces from 5.2.3 (see https://www.scintilla.org/ScintillaHistory.html), please use SCI_GETTEXTRANGEFULL, SCI_FINDTEXTFULL,SCI_GETSTYLEDTEXTFULL and SCI_FORMATRANGEFULL and corresponding defines/structs

Do you consider that as a major issue?

[alankilborn]

Do you consider that as a major issue?

"major"...well, no, I guess not.

But now all Pythonscript programmers are going to have to carry along the "Full" part (i.e., getTextRangeFull), which just feels awkward. As the arguments and return value are the same (at the Python level) for the old getTextRange and the current getTextRangeFull, it would have been nice for the plugin itself to convert calls to the former into the latter, as a convenience to the programmer.

[alankilborn]

Workaround:

Put the following in user startup.py:

editor.getTextRange = editor.getTextRangeFull
editor1.getTextRange = editor1.getTextRangeFull
editor2.getTextRange = editor2.getTextRangeFull

[gxhhaley]

i want a release download

[Ekopalypse]

@gxhhaley - What do you mean? This?

[chcg]

@alankilborn added getStyledText(), findText(), getTextRange() again as substitutes to their corresponding Full versions. Hope that is fixing it for you, see https://github.com/bruderstein/PythonScript/releases/tag/v3.0.24 . Sorry for the long delay for it.