Updated VisualNEO Win SDK (Delphi 10)
Quote from luishp on January 7, 2019, 3:55 pmI have just uploaded a new VisualNEO Win SDK for Delphi 10.
As there is now a free Delphi Community Edition, I hope more developers will become interested in developing new plugins.
The updated version has been kindly provided by NeoSoftware.
I have just uploaded a new VisualNEO Win SDK for Delphi 10.
As there is now a free Delphi Community Edition, I hope more developers will become interested in developing new plugins.
The updated version has been kindly provided by NeoSoftware.
Quote from HPW on January 7, 2019, 5:45 pmHello Luis,
Thanks to you and Dave for the update.
I have not installed Delphi 10 yet. But this may change in the future. ;-)
Might it be compatible with a Delphi XE3 ?
Regards
Hans-Peter
Hello Luis,
Thanks to you and Dave for the update.
I have not installed Delphi 10 yet. But this may change in the future. ;-)
Might it be compatible with a Delphi XE3 ?
Regards
Hans-Peter
Quote from luishp on January 7, 2019, 5:52 pmMight it be compatible with a Delphi XE3 ?
I have no idea, sorry.
I haven't had time to test it yet.
Might it be compatible with a Delphi XE3 ?
I have no idea, sorry.
I haven't had time to test it yet.
Quote from as3856 on January 9, 2019, 8:12 amHello luis
Good news, thanks to you and Dave for the update.
I just have free Delphi Community Edition.
Hello luis
Good news, thanks to you and Dave for the update.
I just have free Delphi Community Edition.
Quote from Ruben Vis on December 30, 2021, 11:40 amTo all Delphi-Plugin developers,
After compiling either Delphi example for VisualNeo Win, I noticed that the plugin Name, Description, actions and code-hints (basically all strings that are shared between plugin and host), only displayed their first character.
Delphi version in use: 10.4 Version 27.0.40680.4203
Taking the Calendar-example, I found that after selecting the VNW-rectangle, the text box would display a couple of chinese characters.
Although I am thus far unable to compile a fully working calendar plugin, I have found that the Delphi definition for PCHAR has changed between latest Delphi and the release of the SDK, and changing this to a more compatible type fixes the fact that only one character of interchanged strings gets passed.
PCHAR being the datatype of string(pointer)s that are exchanged between the plug and VNW, should be replaced with PAnsiChar to produce the desired result.
I am posting this to spare any aspiring Delphi VNW-plugin developer some time; it took me about 3 hours to find out about this definition change in Delphi, formulate the hypothesis and testing it.
Attached is the Calendar Example in which I have managed to fix the plugins actions, and the actions description, for full transparency.If I have managed to change the plugins' name and description, and tested its full functionality, I promise to do another upload.
Happy coding,
Best regards,
Ruben.
To all Delphi-Plugin developers,
After compiling either Delphi example for VisualNeo Win, I noticed that the plugin Name, Description, actions and code-hints (basically all strings that are shared between plugin and host), only displayed their first character.
Delphi version in use: 10.4 Version 27.0.40680.4203
Taking the Calendar-example, I found that after selecting the VNW-rectangle, the text box would display a couple of chinese characters.
Although I am thus far unable to compile a fully working calendar plugin, I have found that the Delphi definition for PCHAR has changed between latest Delphi and the release of the SDK, and changing this to a more compatible type fixes the fact that only one character of interchanged strings gets passed.
PCHAR being the datatype of string(pointer)s that are exchanged between the plug and VNW, should be replaced with PAnsiChar to produce the desired result.
I am posting this to spare any aspiring Delphi VNW-plugin developer some time; it took me about 3 hours to find out about this definition change in Delphi, formulate the hypothesis and testing it.
Attached is the Calendar Example in which I have managed to fix the plugins actions, and the actions description, for full transparency.
If I have managed to change the plugins' name and description, and tested its full functionality, I promise to do another upload.
Happy coding,
Best regards,
Ruben.
Uploaded files:- You need to login to have access to uploads.
Quote from luishp on December 30, 2021, 11:56 amThanks so much @ruben-vis!!
Thanks so much @ruben-vis!!
Quote from albertomeyer on December 30, 2021, 3:12 pm:) just use PAnsichar andPAnsiString.
It is a 1 minute fix
:) just use PAnsichar andPAnsiString.
It is a 1 minute fix
Quote from albertomeyer on December 30, 2021, 3:53 pmMy post is about the fact that the change is very simple, not the friend taking a long time to find it. Some bugs, for example, take hours to fix
My post is about the fact that the change is very simple, not the friend taking a long time to find it. Some bugs, for example, take hours to fix
Quote from Ruben Vis on December 30, 2021, 6:34 pmQuote from albertomeyer on December 30, 2021, 3:12 pm:) just use PAnsichar andPAnsiString.
It is a 1 minute fix
As far as getting said strings interchanged it is, I found I had to swap out or cast about 15-20 more instances of to completely rid the build/compilation of errors and warnings... and after that I noticed that the VNW-rectangle-select button in the plugins form still throws an access-violation.
If I am permitted, I would like to publish the source code in a public git-hub repository, as I expect many more changes to the source code need to be made and some sort of version management will prove itself useful... full credits to SinLios off course.
Quote from albertomeyer on December 30, 2021, 3:12 pm:) just use PAnsichar andPAnsiString.
It is a 1 minute fix
As far as getting said strings interchanged it is, I found I had to swap out or cast about 15-20 more instances of to completely rid the build/compilation of errors and warnings... and after that I noticed that the VNW-rectangle-select button in the plugins form still throws an access-violation.
If I am permitted, I would like to publish the source code in a public git-hub repository, as I expect many more changes to the source code need to be made and some sort of version management will prove itself useful... full credits to SinLios off course.
Quote from luishp on December 30, 2021, 7:34 pm@ruben-vis thanks so much! Please let us know the URL to the repository once you publish it.
I will share it in the external resources section. With credits to you, off course :)
@ruben-vis thanks so much! Please let us know the URL to the repository once you publish it.
I will share it in the external resources section. With credits to you, off course :)
Quote from albertomeyer on December 30, 2021, 11:10 pmQuote from Ruben Vis on December 30, 2021, 6:34 pmQuote from albertomeyer on December 30, 2021, 3:12 pm:) just use PAnsichar andPAnsiString.
It is a 1 minute fix
As far as getting said strings interchanged it is, I found I had to swap out or cast about 15-20 more instances of to completely rid the build/compilation of errors and warnings... and after that I noticed that the VNW-rectangle-select button in the plugins form still throws an access-violation.
If I am permitted, I would like to publish the source code in a public git-hub repository, as I expect many more changes to the source code need to be made and some sort of version management will prove itself useful... full credits to SinLios off course.
I use a VERY modified version of the SDK, made speacially to my needs, but a fixed version for the SDK will be very useful for new commers
Quote from Ruben Vis on December 30, 2021, 6:34 pmQuote from albertomeyer on December 30, 2021, 3:12 pm:) just use PAnsichar andPAnsiString.
It is a 1 minute fix
As far as getting said strings interchanged it is, I found I had to swap out or cast about 15-20 more instances of to completely rid the build/compilation of errors and warnings... and after that I noticed that the VNW-rectangle-select button in the plugins form still throws an access-violation.
If I am permitted, I would like to publish the source code in a public git-hub repository, as I expect many more changes to the source code need to be made and some sort of version management will prove itself useful... full credits to SinLios off course.
I use a VERY modified version of the SDK, made speacially to my needs, but a fixed version for the SDK will be very useful for new commers