Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
1
Registration and Setup / Re: Installing PxPlus on Azure or Sharepoint
« on: September 22, 2023, 09:24:44 AM »
For clarification, as of PxPlus 2023 (v20) the standard PxPlus/Nomads security module provides multi-factor authentication using either email or SMS.
For details see:
https://manual.pvxplus.com/page/NOMADS%20Graphical%20Application/System%20Maintenance%20Tools/Security%20Manager/Two%20Factor%20Authentication.htm
For details see:
https://manual.pvxplus.com/page/NOMADS%20Graphical%20Application/System%20Maintenance%20Tools/Security%20Manager/Two%20Factor%20Authentication.htm
2
Nomads / Re: Nomads Library Key - Byte (13,1)
« on: September 11, 2023, 02:14:06 PM »
You can find this in *winproc.dsp -- but basically.
F - Would indicate a control since F is a valid HEX character
R - Is for Drag/Drop logic
S - Substitute panels
V - Dependency tables
Y - Independent Cell/Row logic for Grids
F - Would indicate a control since F is a valid HEX character
R - Is for Drag/Drop logic
S - Substitute panels
V - Dependency tables
Y - Independent Cell/Row logic for Grids
3
Nomads / Re: Nomads Library Key - Byte (13,1)
« on: September 08, 2023, 11:52:37 AM »
Columns 13,4 are used to effectively sort the panel definition based on line/column so when drawing the controls get created from top left thru bottom right. The logic basically converts the column / line to their standard numeric value ("00"->"99") or if they exceed 100 they are replaced with a hex value meaning the first byte (13) will not exceed "F" as the lines number is not allowed to be greater than 255.
Other panel information such as grid presets, menus, etc will have values whose first character (byte 13) is above "F" and indicates the type of information.
Other panel information such as grid presets, menus, etc will have values whose first character (byte 13) is above "F" and indicates the type of information.
4
Language / Re: 'DROP' mnemonic with ERR= clause
« on: September 05, 2023, 03:22:31 PM »
Technically the 'DROP' mnemonic is really just a function that returns the escape sequence required to drop the specified window.
For example its perfectly legal to code:
X$ = 'DROP'(win_num)
This will result in an escape sequence that can be output to console (channel 0). Any/all mnemonics are really just escape sequences that can be output to a device.
As for the ERR= clause, it would have been triggered if the window number was invalid (such as a negative number or non-integer)
For example its perfectly legal to code:
X$ = 'DROP'(win_num)
This will result in an escape sequence that can be output to console (channel 0). Any/all mnemonics are really just escape sequences that can be output to a device.
As for the ERR= clause, it would have been triggered if the window number was invalid (such as a negative number or non-integer)
5
Language / Re: 'DROP' mnemonic with ERR= clause
« on: September 05, 2023, 02:32:56 PM »
The ERR= should be on the print, not on the mnemonic.
e.g. PRINT (0,ERR-*next) 'DROP'(Win_num),
e.g. PRINT (0,ERR-*next) 'DROP'(Win_num),
6
Programming / Re: performance of select record
« on: September 05, 2023, 10:31:46 AM »
Just a side note.
As Stephane stated the select does not attempt to determine the best key to use. It was designed for speed and therefore assumes the programmer will pre-identify which key would be optimal.
Having the system analyze a request such as a SELECT to determine the key to use is basically a waste of system resources. The programmer should know up front which key would be best so why have the system try and figure this out every time it hits the SELECT statement?
Its fine for a generic query system SELECT to figure out which key to use, but for a program it makes more sense for the programmer to state which key the system should use to assure consistent results.
To simplify this the system supports named keys so that the file/table can have its keys altered and the programmer will not need to adapt the code to different key numbers. For example if you want the access by name, then name the key something like "ByName" and opposed to key number 'nnn'.
As Stephane stated the select does not attempt to determine the best key to use. It was designed for speed and therefore assumes the programmer will pre-identify which key would be optimal.
Having the system analyze a request such as a SELECT to determine the key to use is basically a waste of system resources. The programmer should know up front which key would be best so why have the system try and figure this out every time it hits the SELECT statement?
Its fine for a generic query system SELECT to figure out which key to use, but for a program it makes more sense for the programmer to state which key the system should use to assure consistent results.
To simplify this the system supports named keys so that the file/table can have its keys altered and the programmer will not need to adapt the code to different key numbers. For example if you want the access by name, then name the key something like "ByName" and opposed to key number 'nnn'.
7
Wish List / Re: Weeknumbers in multiline-calendar
« on: September 05, 2023, 10:23:36 AM »
Its possible we could look at this however the issue with week numbers is what is week 1.
Is it the week that contains Jan 1, the week with the first Monday (or Sunday) in the year...
Different systems use different starting weeks.
Is it the week that contains Jan 1, the week with the first Monday (or Sunday) in the year...
Different systems use different starting weeks.
8
Programming / Re: performance of select record
« on: August 24, 2023, 01:18:58 PM »
Not certain how you ran your test but I just did the following:
-}list
0010 OPEN (1,IOL=*)"bigfile"
0020 LET rd=0,sel=0
0030 LET x=TMR(0)
0040 READ (1,END=0070)
0050 rd++
0060 GOTO 0040
0070 PRINT TMR(0),rd
0080 CLOSE (1)
0090 LET x=TMR(0)
0100 SELECT * FROM "bigfile"
0110 sel++
0120 NEXT RECORD
0130 PRINT TMR(0),sel
-}run
1.241 114697
1.089 114697
-}run
1.245 114697
1.088 114697
-}run
1.237 114697
1.087 114697
As you can see the SELECT was faster even considering the SELECT timing included the file open/close..
-}list
0010 OPEN (1,IOL=*)"bigfile"
0020 LET rd=0,sel=0
0030 LET x=TMR(0)
0040 READ (1,END=0070)
0050 rd++
0060 GOTO 0040
0070 PRINT TMR(0),rd
0080 CLOSE (1)
0090 LET x=TMR(0)
0100 SELECT * FROM "bigfile"
0110 sel++
0120 NEXT RECORD
0130 PRINT TMR(0),sel
-}run
1.241 114697
1.089 114697
-}run
1.245 114697
1.088 114697
-}run
1.237 114697
1.087 114697
As you can see the SELECT was faster even considering the SELECT timing included the file open/close..
9
Programming / Re: MS Explorer extra columns accessibl to PX+?
« on: August 17, 2023, 02:29:54 PM »
To the best of our knowledge this information is obtained by Windows actually opening and reading the file contents based on the file prefix/header.
The directory entries themselves contain little more than file name, size, create/access/change dates, and permissions.
You would need to open each file and extract the information based on the type of contents.
The directory entries themselves contain little more than file name, size, create/access/change dates, and permissions.
You would need to open each file and extract the information based on the type of contents.
10
Thin Client/WindX / Re: pxplus.exe as Citrix-App
« on: August 15, 2023, 09:38:31 AM »
We have had no reports of any problem like what you describe, and the fact that only 3 of 300 have this issue would tend to suggest it is something in either the Citrix or workstation setup.
How long is the invocation string? Older software often limited the OS command line to 256, is it possible the clients that fail are running older software? (PxPlus dynamically allocates the command line buffer internally thus it is only limited by the OS)
How long is the invocation string? Older software often limited the OS command line to 256, is it possible the clients that fail are running older software? (PxPlus dynamically allocates the command line buffer internally thus it is only limited by the OS)
11
Thin Client/WindX / Re: Windx on a MAC
« on: August 02, 2023, 11:39:36 AM »
One other option for an M1 -- they could use Microsoft's remote desktop to connect to a Windows machine which would run the application. Technically the application won't be running on the Mac but from a user perspective they only need one machine on their desk.
We here use RDP to Windows machines on an M1 in the office and it works fine other than the mouse wheel is different (which is normal for a Mac).
We here use RDP to Windows machines on an M1 in the office and it works fine other than the mouse wheel is different (which is normal for a Mac).
12
Thin Client/WindX / Re: Windx on a MAC
« on: August 01, 2023, 10:04:21 AM »
The only option we have for graphical application on M1 Macs is via a browser using iNomads or a PxPlus Web application.
Text mode will run fine on an M1 system
Text mode will run fine on an M1 system
13
Nomads / Re: Possible Nomads Variable Values
« on: July 24, 2023, 03:49:51 PM »
While we prefer you don't change/alter these value outside of Nomads, the OBJ_STS$ variable contains what we will be setting in the OPT= when we create the control.
As such you can look up at https://manual.pvxplus.com what the various codes mean. For example:
https://manual.pvxplus.com/page/directives/multi_line.htm#Mark4
https://manual.pvxplus.com/page/directives/list_box.htm#Mark5
https://manual.pvxplus.com/page/directives/grid.htm#Mark4
(The bookmarks labels #Marknn vary and are optional)
As such you can look up at https://manual.pvxplus.com what the various codes mean. For example:
https://manual.pvxplus.com/page/directives/multi_line.htm#Mark4
https://manual.pvxplus.com/page/directives/list_box.htm#Mark5
https://manual.pvxplus.com/page/directives/grid.htm#Mark4
(The bookmarks labels #Marknn vary and are optional)
14
Webster Plus / New Webster+ Video and Demo site
« on: August 20, 2021, 02:17:29 PM »
See Webster+ in action!
We are pleased to announce the latest in the Webster+ videos and even more excited to announce the Webster+ demo application.
In this short five minute video, we are introducing our very own Webster+ demo application. What better way to see what you can do with Webster+ than with a working application.
Watch Video
You'll also learn how you can take a self-guided tour of the application which uses a wide variety of Webster+ features from simple generated file maintenance pages to grids, smart charts, report writer and much more.
Take the demo application for a test drive at https://testdrive.pvxplus.com
We are pleased to announce the latest in the Webster+ videos and even more excited to announce the Webster+ demo application.
In this short five minute video, we are introducing our very own Webster+ demo application. What better way to see what you can do with Webster+ than with a working application.
Watch Video
You'll also learn how you can take a self-guided tour of the application which uses a wide variety of Webster+ features from simple generated file maintenance pages to grids, smart charts, report writer and much more.
Take the demo application for a test drive at https://testdrive.pvxplus.com
15
iNomads / Re: Inomads Error
« on: August 20, 2021, 10:20:48 AM »
Well the error is being reported by in_xeq which itself doesn't do anything except perform the logic defined in your panel. In this case its a PERFORM "VIEW_M;Init".
We would suggest you put a trace in your program VIEW_M at the label Init to see what could be happening.
We would suggest you put a trace in your program VIEW_M at the label Init to see what could be happening.