Evidently, PxPlus now ships with Gord's Print Preview as the standard driver selected for *viewer*. There doesn't seem to be any property controlling text copy capabilities. Copying/saving of [PDF] files, yes; text, no.
I think I found the viewer driver you were mentioning. It has 4 zoom levels, and allows copying to the clipboard - of the entire file. There is no select+copy. With some work, though, I can probably get that going, as well as some different zoom controls.
Thanks for pointing this out. I thought there was something like this around.
Not sure if the PDF/View option would be viable in our situation. I can review that, too.

Stay safe!

Look like what I need. Thank you!

Is there a way to prevent a tab on a folder from being created based on Pre-Display factors? Example: Prevent the tab from being created based on whether contingent files exist. If the file(s) exist, create the tab, else skip it.
Thanks!

v13.10 almost on v17
Linux RH

One other thing I'm noticing:

While PxPlus seems to read the pxplus.ini file from the location of the .windx file, icon specification is inconsistent. The shortcut to the .windx file specifies our logo .ico file, which is in the local *lib/bmp folder. That is what we see on the shortcut. It is also what is specified in the pxplus.ini file, which appears on the window caption. However, when we create a dialogue with opt="i", we're getting a PxPlus icon (attached) on the Windows taskbar instead of our logo. Dropping opt="i" puts the correct logo on the caption and the taskbar.

We want to be sure the correct icon shows up whether we include it on the caption or not. Don't want the users confused. Any suggestions/insights?

Devon:
Thanks for the clarification. I'm so used to only working with server-side programs, the fact that "launcher" was client-side only didn't click. I've got the Connection Manager running now, though I'm not yet sure how much it will do for us in the future.

Mike:
It's just taken a little time to wrap my head around some of the ways the process works. I've read through it multiple times, but until I actually saw it "in action", I wasn't getting it. With the Connection Manager "connection", I think we've got something that will keep us going.
The web shortcut sounds intriguing, but would require a LOT of additional work on our end to get the registries updated, etc. Going with a desktop shortcut to the .windx file looks like the quickest, easiest, and most direct route.

Thanks, all, for the help!

While we can get where we are when outputing to a serial file by checking KEC() for the file, is there a way to determine how many characters have been sent to a piped channel? If I open (ch)"|process_prog...", can I know how much went out before I close (ch)?

Thanks!

We're (finally!) upgrading our system from PxPlus v13 to v17. Much of what we have is still legacy character-based. However, the panels we have developed seem to throw Error #88 most of the time. I know there were some changes over the versions. Is there something we need to do to get things working right?