problem with integration of new cse-validator pro

[Gorky]

Hi after upgrading from cse-validator pro 11 to version 12, my webuilder (2011, vers. 11.3) no longer "finds" the new cse-validator ("you must have verion 8 or new "), I tried to both reinstall cse-validator as well as webuilder.

any hints?

thanks

Gorky

p.s. notetab pro integrates the new cse-validator well.I am on windows 7 64 bit

[Karlis]

Seems that the author of CSE has changed the integration API (again). We will take a look at this, most likely this will be corrected in version 2014 beta or preview.

[HTMLValidator]

Seems that the author of CSE has changed the integration API (again). We will take a look at this, most likely this will be corrected in version 2014 beta or preview.

Hello Karlis,

As far as I recall, the CSE HTML Validator API has always maintained backward compatibility when adding new functionality, so I doubt this is the issue.

[Nikolajs]

Meanwhile you can do the following:

1) Select Options > Preferences from the main menu.
2) Choose External Tools > External Programs entry in the options tree on the left.
3) Click Add button to add a new external program, a dialog box will appear.
4) Enter the Title (CSE HTML Validator).
5) Click Browse and point to CSE HTML Validator executable file. By default, CSE HTML Validator is located in c:\\Program Files\\HTMLValidator120\\cse120.exe. Make sure to select cse120.exe executable file.
6) Enter %file in the Parameters field. This will allow you to pass currently opened file to CSE HTML Validator.
7) Click OK.
Click OK to save Options.

Now you can launch CSE HTML Validator from the main menu. See Tools > External Programs > CSE HTML Validator.

[Gorky]

Seems that the author of CSE has changed the integration API (again). We will take a look at this, most likely this will be corrected in version 2014 beta or preview.

Hello Karlis,

As far as I recall, the CSE HTML Validator API has always maintained backward compatibility when adding new functionality, so I doubt this is the issue.

The new version 12 of the cse-validator pro works well with notetab pro 7 and topstyle 4 on the same pc. So dear folks from Blumentals Software please fix asap [its a long way from now to 2014 ]

thanks

Gorky

[Gorky]

Meanwhile you can do the following:

...
5) Click Browse and point to CSE HTML Validator executable file. By default, CSE HTML Validator is located in c:\\Program Files\\HTMLValidator120\\cse120.exe. Make sure to select cse120.exe executable file.
...

Now you can launch CSE HTML Validator from the main menu. See Tools > External Programs > CSE HTML Validator.

for other users: the default path is c:\program files (x86)\HTMLValidator120\cse120.exe
ok thats a dirty hack, but no integration

Gorky

[Karlis]

Working on this right now... Seems that CSE DLL no longer exports some functions, so we had to change the header file.

The wait won't be long.

[HTMLValidator]

Working on this right now... Seems that CSE DLL no longer exports some functions, so we had to change the header file.

The wait won't be long.

Hi Karlis,

I'm curious, can you be more specific? What functions are not being exported anymore? If this is an issue with CSE HTML Validator, then I'd like to fix it.

[Karlis]

It is not an issue with CSE HTML Validator, even not with the API as such. It is an issue with DLL imports. There is no more CSEGetString / CSESetString (these were available in old versions). Although we do not use them (have never used), it was listed in the imports section of the old header and the DLL loading code interpreted this missing function as an indicator that the DLL file is no good because there are missing features (usually newer DLL versions have all the old stuff + new stuff, but in this case some of the old stuff is missing and the "smart" DLL loading code got confused). No biggie, but enough to break...

[HTMLValidator]

It is not an issue with CSE HTML Validator, even not with the API as such. It is an issue with DLL imports. There is no more CSEGetString / CSESetString (these were available in old versions). Although we do not use them (have never used), it was listed in the imports section of the old header and the DLL loading code interpreted this missing function as an indicator that the DLL file is no good because there are missing features (usually newer DLL versions have all the old stuff + new stuff, but in this case some of the old stuff is missing and the "smart" DLL loading code got confused). No biggie, but enough to break...

Thanks for the clarification.

I can tell you that I removed "CSEsetString" and added "CSESetString" because the case was wrong on the function. I just discovered the case for CSEgetString is wrong too... I'm not sure how this happened.

I will bring back the incorrect function names and also add the correct ones to provide maximum compatibility, but the only programs that should be affected by this would be the ones that don't use the wide string functions. Perhaps yours does use only the wide string functions but it was still not liking the change, perhaps due to your "smart" loading.

I guess you could say there was an issue on both ends.

[Karlis]

Yes, you are completely right and correct on all points.

Version 2014 of our code editor uses wide strings. Version 2011 does not, but I'll try to release a patched copy of version 2011 as well so everybody is happy.

[Gorky]

... but I'll try to release a patched copy of version 2011 as well so everybody is happy.

thats good news

thanks
Gorky

[HTMLValidator]

Version 2011 does not, but I'll try to release a patched copy of version 2011 as well so everybody is happy.

Sounds good. For maximum compatibility with this problem in some versions of CSE HTML Validator, I recommend that you try the properly named functions first - "CSEGetString" and "CSESetString", but if they don't exist, then use these if they exist: "CSEgetString" and "CSEsetString". If neither exists, then I guess you're in trouble.

[Karlis]

Starting from this Friday you can download version 11.4 which fixes this issue. Uploading as I write this post...

[Gorky]

Hi Karlis,

thank you very much for fast support. integration now works like a charm (again)

Gorky