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.
946
Programming / Re: File maintenance panel creation for flat files,
« on: July 24, 2018, 08:50:49 AM »
Not certain what you mean by 'Flat' files -- are you referring to Serial/text files? If so the file maintenance system is designed to work with keyed files and not serial files.
If you do mean keyed files, then you should be able to set the global variable before running the file maintenance generator. Once the pane/program is generated it will use whatever is in your global variables.
If you do mean keyed files, then you should be able to set the global variable before running the file maintenance generator. Once the pane/program is generated it will use whatever is in your global variables.
947
Wish List / Re: Forum Notifications
« on: July 20, 2018, 04:29:00 PM »
We decided it was better to split on major components since we have some clients that don't use iNomads, some don't use Nomads, etc...
We tried to keep the number of categories to a manageable level. Having some basic sections allows users to only monitor those sections that may impact them. Plus some boards such as "Off Topic" or "Wish List" are more suited to casual inquiry as opposed to sending email notifications.
About the only area where it might make some sense to merge sections would be "FAQ" and "Tips and Techniques"; but here too we felt the breakdown was better:
We tried to keep the number of categories to a manageable level. Having some basic sections allows users to only monitor those sections that may impact them. Plus some boards such as "Off Topic" or "Wish List" are more suited to casual inquiry as opposed to sending email notifications.
About the only area where it might make some sense to merge sections would be "FAQ" and "Tips and Techniques"; but here too we felt the breakdown was better:
- FAQ for problems and issues people may be having or have reported.
- Tips and Techniques for ways you can improve your application you may not be aware of.
948
Wish List / Re: Forum Notifications
« on: July 20, 2018, 03:57:44 PM »
Thanks for the suggestion. We just enabled notification for the FAQ and Tech Tips so you should be good to go now.
949
Registration and Setup / Re: Version Discrepancy
« on: July 19, 2018, 06:05:40 PM »
First off this, based on what you sent to our support department, this appears to be an INFOR serial number thus you need to contact INFOR about what to install to run their application.
While they generally use standard PxPlus builds they have on occasion used custom builds to address certain issues they were having or to provide special functionality they may have required. INFOR can also advise and supply the WindX which works correctly with their application.
As for software activation, this too needs to be done through INFOR as they have unique activation software that not only activates PxPlus, but also their application which has its own security protection.
With regards to your activation levels, activation keys for newer versions of PxPlus will allow you run older versions of PxPlus. The activation level on the key ONLY establishes the functionality you have been authorized to use. Any PxPlus activation key will allow you to install and run versions of PxPlus up to the level specified in the key, and in addition you can use newer versions of the executable components (Not the library) in order to obtain fixes .
For example a version 10 key will run any version of PxPlus up to and including version 10. It will also allow you to run the version 11 thru 13 executables (EXE/DLL and equivalent on Linux) in order to get access to corrections. If a problem was found in the version 10 executable and was fixed in the version 11 executable, you could install/run the newer executable in order to obtain that fix. This is valid for 3 versions which covers the product support window. Beyond three versions you need to purchase a version upgrade(s) or be on a maintenance program.
Finally, as the serial number you reported on our help desk is from INFOR and you are having trouble, we suggest you contact them for assistance as they can provide the proper versions to install and run along with the proper activation keys.
While they generally use standard PxPlus builds they have on occasion used custom builds to address certain issues they were having or to provide special functionality they may have required. INFOR can also advise and supply the WindX which works correctly with their application.
As for software activation, this too needs to be done through INFOR as they have unique activation software that not only activates PxPlus, but also their application which has its own security protection.
With regards to your activation levels, activation keys for newer versions of PxPlus will allow you run older versions of PxPlus. The activation level on the key ONLY establishes the functionality you have been authorized to use. Any PxPlus activation key will allow you to install and run versions of PxPlus up to the level specified in the key, and in addition you can use newer versions of the executable components (Not the library) in order to obtain fixes .
For example a version 10 key will run any version of PxPlus up to and including version 10. It will also allow you to run the version 11 thru 13 executables (EXE/DLL and equivalent on Linux) in order to get access to corrections. If a problem was found in the version 10 executable and was fixed in the version 11 executable, you could install/run the newer executable in order to obtain that fix. This is valid for 3 versions which covers the product support window. Beyond three versions you need to purchase a version upgrade(s) or be on a maintenance program.
Finally, as the serial number you reported on our help desk is from INFOR and you are having trouble, we suggest you contact them for assistance as they can provide the proper versions to install and run along with the proper activation keys.
950
Programming / Re: system_help
« on: July 19, 2018, 03:46:37 PM »
Yes, to clarify the SYSTEM_HELP always invokes the workstations OS to assist in the opening of the file thus the file must reside on the workstation.
This is done and any graphical application the system has to launch to service/open the file would need to run on the workstation.
This is done and any graphical application the system has to launch to service/open the file would need to run on the workstation.
951
Programming / Re: Invoke PDF at Bookmark
« on: July 17, 2018, 06:03:49 PM »
Additional note -- your PxPlus 2017 should have a *browser control -- it came standard with PxPlus and should have been installed automatically.
Make sure your license is for PxPlus 2017 (V14).
Make sure your license is for PxPlus 2017 (V14).
952
Programming / Re: Invoke PDF at Bookmark
« on: July 17, 2018, 05:37:55 PM »
The OS interface provided by Windows does not allow the passing of a page or bookmark as the interface within Windows looks at the prefix (i.e. http://) or the suffix (last dot onwards such as .exe, .pdf, ...). You have neither a recognizable prefix nor suffix thus the OS has no idea how to help open the file.
And trying "file://c:/name/of/directory/test.pdf#page=3" doesn't work -- it might if you had Chrome installed and set to respond the the file:// prefix but generally this is IE or EDGE.
And trying "file://c:/name/of/directory/test.pdf#page=3" doesn't work -- it might if you had Chrome installed and set to respond the the file:// prefix but generally this is IE or EDGE.
953
Programming / Re: Invoke PDF at Bookmark
« on: July 17, 2018, 04:29:31 PM »
Another option is to use *browser and pass it the page number or bookmark as in:
This works with Page numbers (#page=nnn) or Named destinations (#name).
Code: [Select]
def object h,@(0,0,80,24)="*browser"
h'navigate2("file://c:/temp/111/test.pdf#page=5")
This works with Page numbers (#page=nnn) or Named destinations (#name).
954
Programming / Re: WAIT FOR EVENT example - Error 49
« on: July 17, 2018, 02:40:02 PM »
Have you checked out the example in ENABLE EVENT?
https://manual.pvxplus.com/page/directives/enable_event.htm
Also, many events only work on Windows.
https://manual.pvxplus.com/page/directives/enable_event.htm
Also, many events only work on Windows.
955
Programming / Re: Is it possible to get the program name and line number from a Linux core dump ?
« on: July 17, 2018, 02:29:59 PM »
I'm sure the information is in the core dump somewhere, but there is no easy way to locate the values.
If the issue is reproducible, then you should be able to setup the log file and replicate the failure. If its a one time failure then it could be anything and potentially not even anything related to your application.
I would setup a log file then watch for the problem to resurface.
One simple technique for the log file is add logic like:
This will create you a daily log file with the day of the week in its name and keep the last 6 (requires the logic to run at least once per day every day).
If the issue is reproducible, then you should be able to setup the log file and replicate the failure. If its a one time failure then it could be anything and potentially not even anything related to your application.
I would setup a log file then watch for the problem to resurface.
One simple technique for the log file is add logic like:
Code: [Select]
DayNo = JUL(0,0,0)
P$ = "/tmp/pxpluslog."+dte(DayNo +1:"%Ws")
ERASE P$,ERR=*NEXT
P$ = "/tmp/pxpluslog."+dte(DayNo :"%Ws")
SERIAL P$,ERR=*NEXT
SETDEV (0) SET "LogFile" TO P$
This will create you a daily log file with the day of the week in its name and keep the last 6 (requires the logic to run at least once per day every day).
956
Programming / Re: Is it possible to get the program name and line number from a Linux core dump ?
« on: July 17, 2018, 11:09:52 AM »
Assuming you are running a PxPlus 2016 or newer, you should be able to define a LOGFILE in your INI and the system will place dump information into that file.
The system will produce a dump whenever the OS detects a fault (such as segfault) and it will contain the program running, call stack, and a list of open files.
Check out this link for further information.
The system will produce a dump whenever the OS detects a fault (such as segfault) and it will contain the program running, call stack, and a list of open files.
Check out this link for further information.
957
Programming / Re: Error=31 in file splitting
« on: July 17, 2018, 10:50:16 AM »
What version of PxPlus are you using also are you using the GUI or Text mode of the SplitFile routine to setup the file splitting?
BTW: An error 31 may be due to the memory limits you have set in your application. Do you issue a START nnn to set the memory limit or take the defaults?
You may get around the problem by setting the 'SZ' system parameter to a larger number of setting 'IZ' to have the system ignore the limitation. Note that setting IZ can cause OS problems should you have a run away process that take all OS memory.
BTW: An error 31 may be due to the memory limits you have set in your application. Do you issue a START nnn to set the memory limit or take the defaults?
You may get around the problem by setting the 'SZ' system parameter to a larger number of setting 'IZ' to have the system ignore the limitation. Note that setting IZ can cause OS problems should you have a run away process that take all OS memory.
958
Wish List / Re: simple XML processing
« on: July 13, 2018, 06:16:20 PM »
While we could look to doing this, I don't follow why you think parsing in an array is easier than the current XML parsing using *obj/xml.
Here is a comparison of JSON versus XML.
First the JSON data:
{ "countries":[
{ "name":"Canada",
"capital":"Ottawa" },
{ "name":"USA",
"capital":"Washington" },
{ "name":"France",
"capital":"Paris" }
] }
Now the code to parse assuming X$ contains the JSON:
Now the XML Data
<country>
<name>Canada</name>
<capital>Ottawa</capital>
</country>
<country>
<name>USA</name>
<capital>Washington</capital>
</country>
<country>
<name>France</name>
<capital>Paris</capital>
</country>
And the code to parse the XML in X$
The total number of lines of code is the same, but the JSON processing is making assumptions that the NAME is not blank to determine the number of entries.
The XML knows the count and by definition will validate missing data whereas the JSON parsing logic would need to be enhanced if it wanted to make sure the capital and name fields were present.
I don't see how parsing XML to an array will make this any easier.
BTW: We have made a few changes to improve the XML object for the next release such as a Value$(tagname$) method which combines the Find_Node and Value$ property and you can pass the XML when creating the object.
This will further simplify the code, when using PxPlus 2019, to:
Here is a comparison of JSON versus XML.
First the JSON data:
{ "countries":[
{ "name":"Canada",
"capital":"Ottawa" },
{ "name":"USA",
"capital":"Washington" },
{ "name":"France",
"capital":"Paris" }
] }
Now the code to parse assuming X$ contains the JSON:
Code: [Select]
dim load array${all}=x$
!
for n=1 to 100000
sfx$="countries."+str(n)+"."
name$=array$[sfx$+"name"]
if name$="" \
then break
print "Country:",name$," capital:",array$[sfx$+"capital"]
next
Now the XML Data
<country>
<name>Canada</name>
<capital>Ottawa</capital>
</country>
<country>
<name>USA</name>
<capital>Washington</capital>
</country>
<country>
<name>France</name>
<capital>Paris</capital>
</country>
And the code to parse the XML in X$
Code: [Select]
oXml=new("*obj/xml" for program) ! Create the object
oXml'Set_XML(x$) ! Load the XML
!
n=oXml'Nodes
for n
oCountry=oXml'Node(n)
print "Country:",oCountry'Find_node("name")'value$," capital:",oCountry'Find_node("capital")'value$
next
The total number of lines of code is the same, but the JSON processing is making assumptions that the NAME is not blank to determine the number of entries.
The XML knows the count and by definition will validate missing data whereas the JSON parsing logic would need to be enhanced if it wanted to make sure the capital and name fields were present.
I don't see how parsing XML to an array will make this any easier.
BTW: We have made a few changes to improve the XML object for the next release such as a Value$(tagname$) method which combines the Find_Node and Value$ property and you can pass the XML when creating the object.
This will further simplify the code, when using PxPlus 2019, to:
Code: [Select]
oXml=new("*obj/xml",x$ for program)
!
n=oXml'Nodes
for n
oCountry=oXml'Node(n)
print "Country:",oCountry'Value$("name")," capital:",oCountry'Value$("capital")
next
959
Nomads / Re: Right-Justified Text for CheckBoxes
« on: July 12, 2018, 06:35:41 PM »
PxPlus auto-scales the check box to match the current text line height.
The actual image is dynamically created in order to make the size correct.
With PxPlus 2017 you can also define a file which has the bitmap images you want to use which will be scaled to fit.
For different colors check boxes just set Backcolor to whatever you want to appear inside the box.
The actual image is dynamically created in order to make the size correct.
With PxPlus 2017 you can also define a file which has the bitmap images you want to use which will be scaled to fit.
For different colors check boxes just set Backcolor to whatever you want to appear inside the box.
960
Programming / Re: search installed Excel
« on: July 12, 2018, 10:32:03 AM »
This sounds like you are over reaching in trying to disable the export to EXCEL if it is not installed. There are MANY program that can read EXCEL files and many that can create them.
Here is a link to page that names but a few.
https://www.lifewire.com/what-is-an-xlsx-file-2622540
Unless you plan to test for all of these, suppressing the import/export could potentially cause problems for clients that don't want/need to have a fully functional EXCEL and are using some of these alternatives.
BTW: On my MAC I have iWork and when I run Windows under Parallels, I can use iWork to open and edit any XLSX file.
Here is a link to page that names but a few.
https://www.lifewire.com/what-is-an-xlsx-file-2622540
Unless you plan to test for all of these, suppressing the import/export could potentially cause problems for clients that don't want/need to have a fully functional EXCEL and are using some of these alternatives.
BTW: On my MAC I have iWork and when I run Windows under Parallels, I can use iWork to open and edit any XLSX file.