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.
166
Language / distinguish errors 0
« on: August 30, 2018, 05:12:57 AM »
Accidently *optsel was called from a cron job, which caused an error 0 in line 260. Due to the nature of an error 0 our errorhandler tried to continue, which will never succeed.
The question is, if that error 0 can be dinstinguished somehow from an error 0 caused by lock/open/extract?
The question is, if that error 0 can be dinstinguished somehow from an error 0 caused by lock/open/extract?
167
Programming / looking for a cancel request
« on: August 29, 2018, 08:29:07 AM »
During long processing we display a "Please wait ..." dialog with an optional cancel button. In many cases the working program logic resides much deeper in the call stack than the front end parts. So these programs have no clue of that button and therefore cannot look for a cancel request of the user.
Is there a way to manage a cancel request though (PxPlus V13 and V14)?
Is there a way to manage a cancel request though (PxPlus V13 and V14)?
168
Nomads / Re: Logic with Numeric Multi_lines
« on: August 17, 2018, 11:14:48 AM »
I'm not sure, but I think I see your point.
The concept of the generator is to handle strings only. That is why it requires you to declare the numeric variables of your file in _numdef$. It is used for generating the numeric values for I/O operations on the fly. Otherwise these values would be lost.
But that shouldn't have any impact on your program logic. It should be possible to use numeric controls and "Auto Refresh". This way the generator logic will needlessly create those numeric variables itself.
The concept of the generator is to handle strings only. That is why it requires you to declare the numeric variables of your file in _numdef$. It is used for generating the numeric values for I/O operations on the fly. Otherwise these values would be lost.
But that shouldn't have any impact on your program logic. It should be possible to use numeric controls and "Auto Refresh". This way the generator logic will needlessly create those numeric variables itself.
169
Wish List / Re: modernize the documentation
« on: August 17, 2018, 05:56:28 AM »
Sorry, but I must post a followup.
Our trainee blunts her teeth with the samples for POS. Taking a look at the sample code I don't believe my eyes. All 10 samples throw error 20. That is not what a documentation is mode for. I fear there are more of these.
We - the senior developer - don't need a correct syntax in order to learn how a new feature works. But the next generation believe what they read.
Well, there is a real call for action.
Our trainee blunts her teeth with the samples for POS. Taking a look at the sample code I don't believe my eyes. All 10 samples throw error 20. That is not what a documentation is mode for. I fear there are more of these.
We - the senior developer - don't need a correct syntax in order to learn how a new feature works. But the next generation believe what they read.
Well, there is a real call for action.
170
Wish List / Re: Create new ddf from datadictionary window
« on: August 10, 2018, 02:06:42 AM »
We also missed that option in the past.
You have 2 options
- #1 -
d=new("*dict/database")
d'createdatabase(pathOfNewDD$)
- #2 -
%z__pvxddf$=pathOfNewDD$; rem double underscore
call "*dict/maint"; rem you will be asked to create an new DD
You have 2 options
- #1 -
d=new("*dict/database")
d'createdatabase(pathOfNewDD$)
- #2 -
%z__pvxddf$=pathOfNewDD$; rem double underscore
call "*dict/maint"; rem you will be asked to create an new DD
171
Nomads / Re: Logic with Numeric Multi_lines
« on: August 10, 2018, 01:52:45 AM »
We use "Auto Refresh" in the header properties and Field_Name / Field_Name$ in the logic. This way you can keep a lean code. If you omit the header property, then you must use the control properties Field_Name.ctl'value($).
172
Wish List / modernize the documentation
« on: August 09, 2018, 02:37:23 AM »
We consider line numbers to be definitely outdated. That's why we configured the environment to throw error 85. That works great. But each new trainee stucks when he/she copies the samples from the documentation in order to learn the language. The young people have grown up with programming languages, which don't use line numbers. Explainig this concept requires the words in the past not later than in the 3rd sentence. As we're working today on programs that will run tomorrow, it seems neccessary to me to mention the old style in the documentation but to modernize the samples.
So, can you please remove the line number references in the samples?
... and please don't use "goto" any more as well.
So, can you please remove the line number references in the samples?
... and please don't use "goto" any more as well.
173
Wish List / Re: gosub SOMEWHERE with a$=b$
« on: July 16, 2018, 01:37:29 AM »
You're right for that simple example. But a call is much slower than a gosub. And in legacy code there is often a need to access much environment data as well. So a gosub is still the first choice.
174
Wish List / simple XML processing
« on: July 13, 2018, 05:27:56 AM »
It would be nice to have the same functionalities for XML as for JSon.
In most cases simple data structures must be processed. It is much easier to iterate over an array than to parse a XML file.
create XML from associative array
DIM(XML_LIST ARR$[All]
create associative array from XML
DIM XML_LOAD ARR$[ALL]=XML$
DIM XMLFILE_LOAD ARR$[ALL]=XMLFile$
In most cases simple data structures must be processed. It is much easier to iterate over an array than to parse a XML file.
create XML from associative array
DIM(XML_LIST ARR$[All]
create associative array from XML
DIM XML_LOAD ARR$[ALL]=XML$
DIM XMLFILE_LOAD ARR$[ALL]=XMLFile$
175
Wish List / gosub SOMEWHERE with a$=b$
« on: July 13, 2018, 04:36:26 AM »
I'd like to have a$ implicitly structured like b$ (iol and xfa) when passed to the subroutine.
This would avoid sequences like the following and put more focus on what to do rather than having to deal with the technical background. Perhaps the syntax can be tweaked for this.
local dim workAddr$ : iol(addr1$)
workAddr$ = addr1$
gosub ADDR_2_FILE
workAddr$ = addr2$
gosub ADDR_2_FILE
This would avoid sequences like the following and put more focus on what to do rather than having to deal with the technical background. Perhaps the syntax can be tweaked for this.
local dim workAddr$ : iol(addr1$)
workAddr$ = addr1$
gosub ADDR_2_FILE
workAddr$ = addr2$
gosub ADDR_2_FILE
176
Programming / Re: search installed Excel
« on: July 12, 2018, 01:43:31 AM »
That was our first approach in the past. But it turned out, that this creates an Excel object thus eating time. And in worse cases the installation process starts. We just want to look for the availability of Excel in order to disable/enable import and export options.
Strange enough, though the call to *win/registry fails, a def object EXCEL,"[WDX]Excel.Application" works on both systems.
Strange enough, though the call to *win/registry fails, a def object EXCEL,"[WDX]Excel.Application" works on both systems.
177
Programming / Re: search installed Excel
« on: June 26, 2018, 11:01:07 AM »
That doesn't work either. There is simply no entry hkey_classes_root\excel, but there are very much entries hkey_classes_root\excel.<something>.
178
Programming / Re: search installed Excel
« on: June 26, 2018, 09:55:35 AM »
That doesn't work here. Neither on the Surface Book (Excel-App), nor on my desktop (Excel 365). We're using PxPlus V14 SCS. Both throw an error 11.
179
Programming / search installed Excel
« on: June 26, 2018, 01:38:07 AM »
Hello List ... oops ... Everyone
Currently we're looking for an installed Excel with
call "[LCL]*win/registry", err = *next, "HKEY_CLASSES_ROOT", "Excel.Application\CurVer", $$, dummy$
This doesn't work for an installed Excel-App.
Looking for a registered extension with
call "[LCL]*win/registry", err = *next, "HKEY_CLASSES_ROOT", "SystemFileAssociations\.xls\shellex", $$, dummy$
is not a possitive replacememt, because OpenOfficeCalc may have registered it.
Does someone know a way how to figure out an installed Excel-App?
Regards
Currently we're looking for an installed Excel with
call "[LCL]*win/registry", err = *next, "HKEY_CLASSES_ROOT", "Excel.Application\CurVer", $$, dummy$
This doesn't work for an installed Excel-App.
Looking for a registered extension with
call "[LCL]*win/registry", err = *next, "HKEY_CLASSES_ROOT", "SystemFileAssociations\.xls\shellex", $$, dummy$
is not a possitive replacememt, because OpenOfficeCalc may have registered it.
Does someone know a way how to figure out an installed Excel-App?
Regards