Look fine.

With the version available from versioninfo the additional data:

<versions> <version number="1.11.34" md5="56a19878b902d25d0c1b12b33d3ba44a"/> <version number="1.11.37" md5="b8dfbf18248c53b9d7e368e013590b55"/> </versions>

is not necessary any longer. I corrected the validation for the x86 version. The click on add hash for the dll was missing in the webinterface.

Currently the validation for x64 also fails. I think that is just a sync issue and should be fine in one hour.

Thanks!
Have just uploaded a hotfix to this version. Those who already downloaded the previous one can compare the sources to find the difference in just one word :) And, actually, that error was there since the beginninmg of v0.5.9.9 dev!

https://github.com/Predelnik/DSpellCheck/releases/tag/v1.3.2 is bundled with N++ 7.5.3 also for x64.

@Alan-Kilborn said:

you just don’t want to use it to make Notepad++ more productive for yourself.

What makes you think I don’t want to use it?
Sure without alternatives I will use it, and if there’ll be a dedicated function
I’ll use it instead, end of story.
More important - what makes you think that scripting is there for myself?
What if I want to write common features that can help a lot of people?
Which is obviously the case with such functionality.
And they probably already define the ‘DwellTime’ for pop-up tips or something? According to Scintilla docs that seems to be the purpose. (though I haven’t
tested it yet).

To me that seems a bit crazy.

No comment

Complainers never win…those that DO win. Whiners never even get noticed, even when they have a legit complaint.

If that was adressed to me - then, mr. philosopher, tell me who are those
who complain about “complainers” and make arbitrarily labeling?

Though little late in reply, but no change needed, if you are dealing with debug build (most of developers deals with debug version). Digital signature checking is guarded now.

HMODULE loadSciLexerDll() { generic_string sciLexerPath = getSciLexerFullPathName(moduleFileName, 1024); // Do not check dll signature if npp is running in debug mode // This is helpful for developers to skip signature checking // while analyzing issue or modifying the lexer dll #ifndef _DEBUG bool isOK = VerifySignedLibrary(sciLexerPath, SCINTILLA_SIGNER_KEY_ID, SCINTILLA_SIGNER_SUBJECT, SCINTILLA_SIGNER_DISPLAY_NAME, false, false); if (!isOK) { ::MessageBox(NULL, TEXT("Authenticode check failed: signature or signing certificate are not recognized"), TEXT("Library verification failed"), MB_OK | MB_ICONERROR); return nullptr; } #endif // !_DEBUG return ::LoadLibrary(sciLexerPath.c_str()); }

Yeah, the header detection needs improvement.
The goal with CsvQuery has always been to detect everything automatically, usually (e.g. Excel and SQL Server) when reading CSV you always have to enter separator char, “has header row” etc.

But this detection can be tricky.
It works by reading 20 lines or so, and try to guess the type of each column.
If the first row had only strings, but all other rows had at least one (common) number column, it assumes the file has a header row. Yeah, not exactly foolproof. There is a reason the only issues in github right now is Better detect header row and Add “has header row” to Manual Parse Settings (so you can force it when it guess wrong) :P

And yes, the MSSQL code use a different header detector right now, since I’m writing a generic one both can use, but the SQLite code still use the old detection.

Regarding the “already an object named ‘this’” error - yeah, bug. SQLite is much more forgiving than MSSQL :)

I’m curious if you determine data types in the plugin, or does sqlite make it’s own guess? How does it know what type to make a column when it imports the csv into SQL Server?

In MSSQL there is currently no (working) type detection. SQLite doesn’t have column types, everything is strings. So “Sum()” etc is done by type converting on the fly. Apparently SQLite can handle euro :)

Many many thanks, i looking for something like it for long time…
Best wishes for you

Add your issue at https://github.com/jeanpaulrichter/nppcrypt/issues to get the necessary attention.

@pnedev
Thanks for the tips. Now it works.
I think I was confused with the two parameters “generic database config” and “current database config”

I’ll use it for several days and i’ll get back to you for some suggestions.