Recent Posts
1
Language / Re: Different Listbox Row Heights with Accented Characters
« Last post by James Zukowski on Today at 03:16:34 PM »This also seems to cause a problem with descenders, too. In the latest example, is that "Hague" or "Haque"?
Does anyone know if this is PxPlus or Windows behavior? Is there some setting I'm not setting?
Does anyone know if this is PxPlus or Windows behavior? Is there some setting I'm not setting?
2
Language / EXTRACT not locking?
« Last post by James Zukowski on Today at 02:32:03 PM »We encountered an interesting situation and could use some clarity and/or confirmation.
Using a Linux server (RHEL 7.9) with PxPlus v15.1 via WindX we open a test file and EXTRACT a record. In another session, open the same file and READ the record. No Error 0.
Upon closer examination, we noticed the Linux file permissions were "-rw-r--r--" and the file was "owned" by a different username. When we changed the permissions to "-rw-rw-rw-", the EXTRACT/READ above worked as expected.
So, it seems that an EXTRACT on a file where a WRITE cannot actually happen is treated as a READ, even though everything, including FIN(ch,"Extract"), suggests the EXTRACT really happened. Except it didn't.
Is this proper? Or is there something missing along the way?
Any guidance would be greatly appreciated.
Thanks!
Using a Linux server (RHEL 7.9) with PxPlus v15.1 via WindX we open a test file and EXTRACT a record. In another session, open the same file and READ the record. No Error 0.
Upon closer examination, we noticed the Linux file permissions were "-rw-r--r--" and the file was "owned" by a different username. When we changed the permissions to "-rw-rw-rw-", the EXTRACT/READ above worked as expected.
So, it seems that an EXTRACT on a file where a WRITE cannot actually happen is treated as a READ, even though everything, including FIN(ch,"Extract"), suggests the EXTRACT really happened. Except it didn't.
Is this proper? Or is there something missing along the way?
Any guidance would be greatly appreciated.
Thanks!
3
Programming / Re: Spawning a session
« Last post by James Zukowski on Today at 08:58:00 AM »And to make things easier for the user, you could include a "Copy" button with each data field which will put it on the clipboard. They could then just click in the field and paste it.
4
Programming / Re: Spawning a session
« Last post by EVa on Today at 03:19:11 AM »As this appears to be a Nomads application, can't you use a concurrent window instead of spawning a new (but completely separate) session ?
5
Programming / Spawning a session
« Last post by Mike Hatfield on Today at 01:34:40 AM »Hi All, I'm running a plus/cs windx session.
I want to be able to open a new window/session from the current program.
In that new window I want to have it run a program that will display some lines of customer information text. When I find the text I want to switch back to the calling windx session and be able type in some of the text. When I'm done I want to close the new window/session either by clicking on the new session 'x' or issuing a close/drop or whatever in the calling program.
Would you believe in the nearly 26 years of programming with Pvx/PxPlus I've never had occasion to do this.
Is this accomplished by spawning a session or is there an easier way. I did do a test with *plus/cs/spawn. It gives me a new session window but none of the global variables from the calling application.
If this is the correct approach how would I place the following in the spawn argument cmdline - PROCESS "ARCM_INFO",%PATH_ROOT$+"dictionary/SM_CZ.EN",R2$
I don't seem to be able to do this with a dialogue window. IE Once inside the dialogue window you can't swith back and forth between the dialogue and calling program.
Thanks
I want to be able to open a new window/session from the current program.
In that new window I want to have it run a program that will display some lines of customer information text. When I find the text I want to switch back to the calling windx session and be able type in some of the text. When I'm done I want to close the new window/session either by clicking on the new session 'x' or issuing a close/drop or whatever in the calling program.
Would you believe in the nearly 26 years of programming with Pvx/PxPlus I've never had occasion to do this.
Is this accomplished by spawning a session or is there an easier way. I did do a test with *plus/cs/spawn. It gives me a new session window but none of the global variables from the calling application.
If this is the correct approach how would I place the following in the spawn argument cmdline - PROCESS "ARCM_INFO",%PATH_ROOT$+"dictionary/SM_CZ.EN",R2$
I don't seem to be able to do this with a dialogue window. IE Once inside the dialogue window you can't swith back and forth between the dialogue and calling program.
Thanks
6
Programming / Re: strange error 61
« Last post by James Zukowski on April 16, 2024, 12:53:18 PM »Have you tried separating the OPEN from the LOCK?
7
Programming / Re: strange error 61
« Last post by Thomas Bock on April 16, 2024, 10:24:31 AM »This is a WindX session and the security options are properly set.
The error occures at random. But how can that be? The file has just been created, so PxPlus must be able to open it.
The error occures at random. But how can that be? The file has just been created, so PxPlus must be able to open it.
8
Programming / Re: strange error 61
« Last post by Devon Austen on April 16, 2024, 07:52:52 AM »One of the reasons for a error 61 is:
• When using WindX, remote access ('WindX authorization') has been denied.
Is this running via WindX?
If so make sure you have your WindX Security setup correctly to not deny access.
For info about WindX security check here:
https://manual.pvxplus.com/?windx/Windx%20Security.htm
• When using WindX, remote access ('WindX authorization') has been denied.
Is this running via WindX?
If so make sure you have your WindX Security setup correctly to not deny access.
For info about WindX security check here:
https://manual.pvxplus.com/?windx/Windx%20Security.htm
9
Programming / strange error 61
« Last post by Thomas Bock on April 16, 2024, 04:35:17 AM »I don't understand why the code below throws an err 61 sometimes
Code: [Select]
BUSY_FILE_NAME$ = "[lcl]Busy.txt"
serial BUSY_FILE_NAME$, err = *next
if tcb(2) {
rem in case the file could not be created ...
} else {
busyFile = hfn
open lock (busyFile) BUSY_FILE_NAME$
rem this throws error 61 ???
}
10
Off Topic / SBOM generation
« Last post by cwellis67 on April 15, 2024, 11:12:49 AM »Has anyone had to create an SBOM for their PxPlus product, and/or does Pvx Plus Technologies provide an SBOM for the language?