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$) ?

Hey, I was having an issue with this but with GET_STR$

I see now if I pass GET_STR$(X$,1)  It returns null and no longer errors out. 

If I pass GET_STR$(X$,0) and X$ was not found in the data, the the error 11 isn't trapped

a serious error in: json.pvc 0484 error 11 results.  Shouldn't that  be trapped either way or did you want a hard error there?

Shouldn't the ,DOM=*NEXT   directive work there or?

Thanks for clarifying.

PvxPlus is here and continuing to develop! They just released ver 22!

Yay! Thank you

Thanks for that SYSTEM_HELP PRINT.  I never knew of this neat PDF print trick interesting... Interesting it used my adobe printer default rather than windows printer.  I'll have to play with this some more.

EDIT: This simulates right clicking pdf and selecting print

You can open the pdf then have them manually print it.

Another way is quite involved:

invoke wait "[wdx]"+quo+EXE$+quo+" /h /n /t "+quo+F$+quo ! +" "+quo+"Microsoft Print to PDF"+quo

EXE$ = executable
F$ = File

You need the EXE for acrobat reader may be able to read registry.  Or can set executable manually.

check for executable

let CC=unt; open (CC,err=*next)"[wdx]C:\program Files\Adobe\Acrobat DC\Acrobat"; close (CC); let EXE$="C:\program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe";


I think you should try to fix the print (OUT) of your report.  Are you sure you have the correct sequence of 'DF' mneumonics, you should be able to get them to match.

print (REP)'font'("Arial",-12),'DF','cpi'(10),'lpi'(6),

When is the new vers coming out?

Excited!

Thanks

Probably a windows thing which windows?  Do you have full line highlight on?

But if your logs show fine from postman then it must be able to communicate with external.

Does by chance the linux have some sort of firewall that is blocking, you should be able to trace that.

Where is the server hosted, is this a firewall issue at this point since postman can get in?  postman is coming in on https?  if so your key is fine then