OK SUCCESS!!  Thank you.

It started working after I rebooted   I tried a second computer and it worked.

Thank you for your help.  I think the key missing component was:

Port needs 22 for SSH

After all that testing I rebooted and it seemed to solve it, I also tested on a second computer also worked!! Thanks

If you could just modify the document to say include port for SSH (Ex 22 next to the simple client thing)

as well: "The remote path of PxPlus on the WindX host (ignored unless Using WindX is set to SSH"

Path sounds like the root dir not including exe itself

Thanks for the help!!

Here's another screen grab

Hey I sure can here's the pics

Set that, same response just spinning and line going across tab bars.

{
    "usingWindx": "SSH",
    "windx.server": "10.1.16.42",
    "windxSsh.user": "palenik",
    "windxSsh.pxplusPath": "/home/palenik/pxp23/pxplus",
    "pxplusPath": "C:\\PVX Plus Technologies\\WindX Plugin-64 2026\\",
    "compiledFileExtension": ".pxp",
    "workbench.editorAssociations": {
        "*.pxp": "default"
    },
    "textProgramFileExtensions": [
        ".pxprg",
        ".pxp"
    ],
    "windx.port": 22
}

Ok, Adding port 22 (#3) may have been part of issue, I got some action but its just spinning now.

{
    "usingWindx": "SSH",
    "windx.server": "10.1.16.42",
    "windxSsh.user": "palenik",
    "windxSsh.pxplusPath": "/home/palenik/pxp23",
    "pxplusPath": "C:\\PVX Plus Technologies\\WindX Plugin-64 2026\\",
    "compiledFileExtension": ".pxp",
    "workbench.editorAssociations": {
        "*.pxp": "default"
    },
    "textProgramFileExtensions": [
        ".pxprg",
        ".pxp"
    ],
    "windx.port": 22
}

ok a text file can open with formatting.

A compiled says unable to find execute activated pxplus.

but still cannot create new.

Hey thanks,

Trying to open a compiled it says its binary and wont open

A text file opens but doesnt seem to do any formatting

Visual Studio Code - Validation with SSH / Windx

I just can't get this to work on my linux machine.
When I "Create a file" It just does nothing empty no response.

PS.  I am using a temp activated pvx 2026 server, on the linux machine with windx plugin 2026 as a test.

Neat square buttons but does the default not highlight the button on hover? 

We've implemented svn in linux it's working really well for us now that we got the kinks out.

We basically made two tools, our own svndiff and svncommit

We made use of these two existing tools which were handy:

call "*plus/proj/pxprg;to_cvs",APP_PATH$,OUT_PATH$,LAST.PSWD$

as well as

call "*plus/proj/pxpnl;to_cvs",APP_PATH$,OUT_PATH$,PANELS$

Thanks Mike you're on to something.

In haste I installed pvxplus 32 bit and that's probably why it appears to be able to access HID.DLL

That would mean this DLL is 32 bit and the Windx 64 bit cant access it.

I need to dig in a bit further, Thanks will report.

Trying to use the HID.DLL through WindX and it just wont work (Linux Server)

Locally from pvx works great just cannot seem to work through windx even if I copy the code to the local PC and call "[lcl]scale.pvx",WEIGHT

I was able to create a Python program and Pvx just calls that to get the value.

I just cannot get a handler for it to return.  Is there way to get this to work?  Thank you.

LET HID_GUID$=DIM(16,$00$)
X=DLL("HID.DLL","HidD_GetHidGuid",HID_GUID$)
PRINT X

Thanks Mike.  Setting with 'NE'=0 did the job with the ERR=*NEXT clause BUT only if I disabled my "ERROR_HANDLER"   LOL  Somehow that was overruling it. 

The ,1 still seems to work best with GET_STR after all this.

let X$=J'GET_STR$(Y$,1)

Thanks for the discussions appreciate it!

Well I had 'NE' on, setting it off just brings me back to my program with the same error 11 still.  I was hoping ERR=*NEXT would then work on:

let TEX$=J'GET_STR$("edges."+str(I)+".texture",err=*next)

however it still does not.

The "Try-catch" worked to trap the error, I'm not used to that but could work.

The most elegant solution is just

let TEX$=J'GET_STR$("edges."+str(I)+".texture",1)

It just doesn't feel intuitive for me I would never remember that but I guess I would if I use it more.

Maybe this is normal working with JSON.

Long story short the data coming back sometimes had "edges.XX.texture" and some records, did not so I got the error.  My solution before the ",1" was to just load it into an array and I had no errors after.

Thanks again.

I'm still genuinely concerned about this using the GET_STR$(X$)  and it erroring within pvx code (json.pvc) if the string is not found unless I use GET_STR$(X$,1) vs just GET_STR$(X$) ?