PxPlus User Forum

Main Board => Discussions => Programming => Topic started by: martinp on August 29, 2024, 01:22:37 PM

Title: Visual Studio Code Extension
Post by: martinp on August 29, 2024, 01:22:37 PM
Hey for the license type how can I point this to our linux server, do I have to share the ACTIVATE.PVX through samba ?  This safe? :)
Title: Re: Visual Studio Code Extension
Post by: Devon Austen on August 29, 2024, 02:16:27 PM
The VS Code Extension needs to be given the path to an active PxPlus executable not the activation file. In this first version you can't point it at a remote PxPlus to use it.

We are looking into that as a feature we can add in a update.
Title: Re: Visual Studio Code Extension
Post by: martinp on August 29, 2024, 04:00:35 PM
Thanks!  Is there an interim solution we can use like a development key to the local PC or something?

Is there a real need to even link to a licensed pvx?  I just wonder because it cant really run pvx right? just read/save.. Doesnt the demo pvx plus allow same function?  or am I missing something.
Title: Re: Visual Studio Code Extension
Post by: Stéphane Devouard on August 30, 2024, 09:30:51 AM
Martin

The VSCode extension does require a PxPlus installation and so is Windows only at the moment (I suspect it uses either the .exe or the COM interface to check for syntax errors)

A demo-activated PxPlus is enough though. That's what I've been using since the Software Developer license got cancelled and I was able to use the VSCode extension. I also saw the expiration nag messages when running VSCode so that's why I suppose it needs the interpreter to interface with the language server...
Title: Re: Visual Studio Code Extension
Post by: martinp on August 30, 2024, 10:04:27 AM
Thanks Stephane, I will try the demo license, I was thinking about it but I saw the docs say "fully activated" so I assumed the demo wasn't enough.
Title: Re: Visual Studio Code Extension
Post by: martinp on August 30, 2024, 11:05:59 AM
I tried it im not sure, these have to be text files?

I tried saving a file to text after multiple errors through ED+ somehow I got it and when I load it in Visual Studio Code I dont really see much benefit?

If its in Visual Studio we should avoid line numbers?

Can I see a screen shot of it loaded with a PVX program just to see what a sample program looks like in VS code?  Thanks :)


Title: Re: Visual Studio Code Extension
Post by: Devon Austen on August 30, 2024, 11:26:44 AM
There are screenshots and detailed instructions found in a how to here: https://manual.pvxplus.com?How%20To/How%20to%20Use%20PxPlus%20VS%20Code%20Ext.htm
Title: Re: Visual Studio Code Extension
Post by: martinp on August 30, 2024, 02:57:59 PM
Ok Thanks I didn't realize the PXP demo wasn't registered and I was using the default editor, and that was causing confusion.  This Looks interesting.

Unfortunately I cannot open the files from a mapped drive or UNC from the linux server.  Not sure why I am getting an error #12  if I copy the files locally it works..  I can create a "new" program and it saves, then I cannot re-load it error #12..

could this be linux samba / windows upper/lower case issue?
Title: Re: Visual Studio Code Extension
Post by: martinp on August 30, 2024, 04:26:00 PM
Somehow got it to work if:

I had to map a Drive, it also needs a subdirectory for it to work ie: M:\xyz\    Can't just use M:\  otherwise strange PVX Error #12's