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.
961
Thin Client/WindX / Re: When starting a program the panel is not visible on screen
« on: July 04, 2018, 05:44:07 PM »
Generally when a panel is started by Nomads, the position is determined either by its last panel position (assuming you have persistence enabled -- see below) or the settings on the panel header.
On the panel header you can specify the location of the panel and a line/column specification. There are three options:
Panel Persistence
Nomads provides the ability for the system to remember where you last placed a panel and will attempt to restore it to the same position. This is done generally by setting %Nomads'Panel_Info_Prog$ (%Nomad_Panel_Info_Prog$) to the name of program which will save and recall the panel position.
We supply a program "*winpnl" that does this for you. It preserves the last location a panel was placed by user id in the file called "panel.inf". Simply call *winpnl prior running any Nomads based application and the system will enable persistence.
You can write your own program to do the same if desired, but generally *winpnl provides the necessary functionality.
Your Problem
You indicated that the position is wrong. Is it possible that you have multiple workstations using the same user id? This could cause confusion if you are using the standard *winpnl program.
On the panel header you can specify the location of the panel and a line/column specification. There are three options:
- ABSOLUTE: The panel will be positioned on the current monitor at the line/column specified. The current monitor will be the main monitor for the initial screen or the monitor in use if you currently have a panel/window being displayed.
- RELATIVE: The panel will be positioned using the line/column values as relative positions based on the current panel/window being displayed. If no windows is displayed, then the position will be relative top of the screen. (Note: There is almost ALWAYS a windows logically present even if it is minimized as PxPlus creates a main window during start up and preserves it last location automatically)
- CENTERED: The Line/Column values are ignored. The panel is displayed centered on the current display.
Panel Persistence
Nomads provides the ability for the system to remember where you last placed a panel and will attempt to restore it to the same position. This is done generally by setting %Nomads'Panel_Info_Prog$ (%Nomad_Panel_Info_Prog$) to the name of program which will save and recall the panel position.
We supply a program "*winpnl" that does this for you. It preserves the last location a panel was placed by user id in the file called "panel.inf". Simply call *winpnl prior running any Nomads based application and the system will enable persistence.
You can write your own program to do the same if desired, but generally *winpnl provides the necessary functionality.
Your Problem
You indicated that the position is wrong. Is it possible that you have multiple workstations using the same user id? This could cause confusion if you are using the standard *winpnl program.
962
Language / Re: Best use of 'ES' mnemonic
« on: July 03, 2018, 10:10:48 AM »
If you have a printer where the ESCAPE is other than $1B$ you can set the value of the 'ES' mnemonic in the device driver using the MNEMONIC directive.
For Example:
->open (1) "*memory*
->mnemonic (1) 'es'=$01$
->print (1) 'es'
->read record (1,ind=0) R$
->print hta(R$)
01
->
Changing the mnemonic will not change value of ESC however, only change what will output when you issue the 'ES' mnemonic to the device.
For Example:
->open (1) "*memory*
->mnemonic (1) 'es'=$01$
->print (1) 'es'
->read record (1,ind=0) R$
->print hta(R$)
01
->
Changing the mnemonic will not change value of ESC however, only change what will output when you issue the 'ES' mnemonic to the device.
963
FAQs / What happens during PxPlus start up?
« on: June 29, 2018, 10:36:45 AM »
When a new session of PxPlus starts up a number of programs are run in order to establish the environment and launch your application.
The programs run are as follows:
If you want to set your system parameters, prefix(es), or do other initialization logic you generally will perform this in your start up program in the starting directory for PxPlus. This will be run before your lead program is executed.
Note: As of PxPlus 2014, when using PxPlus Simple CS the system will run your START_UP program after the workstation connects. Prior releases would run it before the connection was established.
The programs run are as follows:
- Internally PxPlus determines the type of terminal being used to run PxPlus and runs its terminal setup program. These are found in *dev directory.
- For Windows this would be *dev/windows
- For WindX connections using Simple CS, NTHost or the Application server this will be *dev/winterm
- For Unix/Linux the system will get the terminal type from the environment variable TERM and run *dev/xxxxx where xxx is the terminal type in lowercase. If this is not found the system will run *dev/termcap which will try to generate the device driver from the system termcap information.
Note: For WindX connections using SSH or Telnet you should set the environment terminal type to winterm or ansi.
The device driver will normally exit by running *TTY to load the device function and edit keys from the keyboard configuration file for the device. This program will also check to see if there is a user device driver in *udev/devicetype and if present run it. - Once the terminal is configured an internal CALL to "*start.up" is executed to do the following
- Call "*plus/start_up" to handle Plus special PxPlus extensions
- Call your start up program specified in the environment variable PVXSTART or "START_UP" if the environment variable not set.
- Check your product activation to see if it is current or needs updating
- Runs the program specified on the command line if any (the "Lead" program found in LPG system variable). If no program is specified the system will drop to the command line prompt.
If you want to set your system parameters, prefix(es), or do other initialization logic you generally will perform this in your start up program in the starting directory for PxPlus. This will be run before your lead program is executed.
Note: As of PxPlus 2014, when using PxPlus Simple CS the system will run your START_UP program after the workstation connects. Prior releases would run it before the connection was established.
964
Off Topic / Re: Mailing List Update
« on: June 28, 2018, 03:50:11 PM »
Unfortunately due to GDPR rules we cannot make the historical emails available as they cannot be edited in any way that would allow removal of any personal information such as persons name or where they work. While this rule would not apply to non-EU member postings, because message threads often include the data submitted by others all emails have the potential to include personal data and not in any form that is easily editable or able to be removed.
If you have things you are looking for we suggest you post your request here and we will try to either answer the question and/or search the archives to get an answer removing any personal data from the response. Over time this should allow this forum to include many items of interest to the community.
This also will allow us to update many of the answers that were in older mail list entries. Older answers may now no longer be relevant or correct as the product has changed over the years. For example older maillist entries might suggest you invoke Adobe to display a PDF or Shell.explorer to display an animated GIF, ignoring the fact that the *BROWSER object module included in PxPlus 2017 can be used to display PDF files and that animated GIF files are supported directly.
If you have things you are looking for we suggest you post your request here and we will try to either answer the question and/or search the archives to get an answer removing any personal data from the response. Over time this should allow this forum to include many items of interest to the community.
This also will allow us to update many of the answers that were in older mail list entries. Older answers may now no longer be relevant or correct as the product has changed over the years. For example older maillist entries might suggest you invoke Adobe to display a PDF or Shell.explorer to display an animated GIF, ignoring the fact that the *BROWSER object module included in PxPlus 2017 can be used to display PDF files and that animated GIF files are supported directly.
965
Thin Client/WindX / Re: Ports to open for WindX.utl SPAWN
« on: June 27, 2018, 01:16:10 PM »
Generally we suggest you use Simple CS to connect to the server as it only requires a single port. The default is 4093 which is defined by ICANN for use by us.
If using Telnet or SSH to connect then by default the system will ask the OS to provide it an available port number which, as you say, can cause trouble with firewall settings.
Now you can override this and force the application to use a specific host/port by setting %PXPLUS_HOST prior calling *windx.utl;spawn. This variable can be set to an asterisk followed by name/address of the host (as seen from Workstation perspective), a semi=colon, then the port number to use.
Example
%PXPLUS_HOST$="*server1.inhouse.net;4093"
Where "server1.inhouse.net" is the host address and 4093 is the port to use.
This is documented at a note on the bottom of https://manual.pvxplus.com/page/windx/windxutl.htm
If using Telnet or SSH to connect then by default the system will ask the OS to provide it an available port number which, as you say, can cause trouble with firewall settings.
Now you can override this and force the application to use a specific host/port by setting %PXPLUS_HOST prior calling *windx.utl;spawn. This variable can be set to an asterisk followed by name/address of the host (as seen from Workstation perspective), a semi=colon, then the port number to use.
Example
%PXPLUS_HOST$="*server1.inhouse.net;4093"
Where "server1.inhouse.net" is the host address and 4093 is the port to use.
This is documented at a note on the bottom of https://manual.pvxplus.com/page/windx/windxutl.htm
966
Wish List / Re: visual classes / textcolour and backcolour when MULTI_LINE has focus / hovered
« on: June 27, 2018, 08:50:33 AM »
While we don't currently have Hover color, there is a FocusBackColor$ and FocusTextColor$ properties on the control that can be set so adding these to the Visual Class options should be no problem.
967
Registration and Setup / Re: Configuring a Pro system to act like Base system
« on: June 27, 2018, 08:45:47 AM »
Unfortunately no -- if your license is Pro then you will get the Pro features (same for ECommerce).
If you would like, perhaps you could add this to our Wishlist section of the forum.
If you would like, perhaps you could add this to our Wishlist section of the forum.
968
Programming / Re: search installed Excel
« on: June 26, 2018, 04:22:09 PM »
You may have to contact Microsoft to have them advise how to tell if Excel-App is installed. Its really not something relative to PxPlus but rather to Windows and how it registers applications.
While the Apps is likely in the C:\Program Files\WindowsApps directory -- this won't help you much as this directory cannot be accessed without Admin privileges.
There may also be a registry entry somewhere but as you are dealing with "Apps" on Windows they may be using some other form of registration process as Apps are installed quite differently than normal windows applications.
Now you might be able to use powershell to get a list of apps installed by executing:
powershell -Command get-appxpackage
While the Apps is likely in the C:\Program Files\WindowsApps directory -- this won't help you much as this directory cannot be accessed without Admin privileges.
There may also be a registry entry somewhere but as you are dealing with "Apps" on Windows they may be using some other form of registration process as Apps are installed quite differently than normal windows applications.
Now you might be able to use powershell to get a list of apps installed by executing:
powershell -Command get-appxpackage
- This should be able to be piped into you PxPlus program
969
Programming / Re: search installed Excel
« on: June 26, 2018, 10:43:51 AM »
Perhaps it is using the 64 Bit version of Excel and since PxPlus is a 32 Bit application the system is checking the 32 bit registry.
The registry accesses may need to be changed to:
call "[lcl]*win/registry;read",err=*next,"hkey_classes_root","excel","",_X$,0,64
The issue of different registries was mentioned in a Topic in the FAQ in the Knowledge base section
https://forum1.pvxplus.com/index.php?topic=22.0
The registry accesses may need to be changed to:
call "[lcl]*win/registry;read",err=*next,"hkey_classes_root","excel","",_X$,0,64
The issue of different registries was mentioned in a Topic in the FAQ in the Knowledge base section
https://forum1.pvxplus.com/index.php?topic=22.0
970
Programming / Re: search installed Excel
« on: June 26, 2018, 08:32:51 AM »
Funny you should ask about this. We are in the middle of adding a similar check to a PxPlus utility due to recent changes in Windows 10.
The logic we are testing is:
So far in our limited testing this appears to work.
The logic we are testing is:
Code: [Select]
call "[lcl]*win/registry;read",err=*next,"hkey_classes_root","excel","",_X$;
if _X$<>"" then print "Excel Installed" So far in our limited testing this appears to work.
971
Off Topic / Re: Hi there!
« on: June 25, 2018, 11:06:09 AM »
Glad you like it. It should make things easier for people while allowing individuals to maintain email notifications if they desire.
We also setup the Knowledge base area and a secondary theme to provide a different look for those who want it.
For our European friends we added the language packs for Dutch, German, Spanish, and French.
We also setup the Knowledge base area and a secondary theme to provide a different look for those who want it.
For our European friends we added the language packs for Dutch, German, Spanish, and French.