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.
196
Language / Re: Accepting variable number of arguments in a function call
« on: January 09, 2020, 01:19:23 PM »
Has the STK(Properties) function been updated to reflect read-only arrays?
197
Programming / Re: viewer display
« on: December 27, 2019, 12:51:35 PM »
It sounds like your program is sending out a 'BR' / 'ER' mnemonic combination for reverse video, which would normally be for a text screen display.
198
Programming / Re: Program Caching
« on: December 20, 2019, 12:34:49 PM »
Probably so, but the situation is more like:
if nul(Prog_FNC$) or fin(Prog_FNC$,"LCL_MTime")>%FNC_Time$ then perform "Update_Prog"
A close(lfo) after the perform is probably not appropriate. As an 'else', perhaps, but the whole thing starts getting very messy-looking for future maintenance, especially with the nul() test.
if nul(Prog_FNC$) or fin(Prog_FNC$,"LCL_MTime")>%FNC_Time$ then perform "Update_Prog"
A close(lfo) after the perform is probably not appropriate. As an 'else', perhaps, but the whole thing starts getting very messy-looking for future maintenance, especially with the nul() test.
199
Programming / Re: Program Caching
« on: December 20, 2019, 11:49:08 AM »
I've worked around doing this in a single statement (though I'd like to get back to that).
It's now an OPEN INPUT; Var$=fin(); CLOSE to get the date/time info for the comparison. Works fine, but a little more than I'd like.
It's now an OPEN INPUT; Var$=fin(); CLOSE to get the date/time info for the comparison. Works fine, but a little more than I'd like.
200
Programming / Re: Program Caching
« on: December 19, 2019, 12:15:33 PM »
I think I figured it out, though it does lead to another question.
In our menu program, I test fin(Prog_FNC$,"LCL_MTime") against a previous global value. This seems to 'open' the (program) file, but not close it. The new question: How can this "file" (Prog_FNC$) be closed?
In our menu program, I test fin(Prog_FNC$,"LCL_MTime") against a previous global value. This seems to 'open' the (program) file, but not close it. The new question: How can this "file" (Prog_FNC$) be closed?
201
Programming / Re: Program Caching
« on: December 16, 2019, 03:43:22 PM »
That's what I would have thought. Evidently, as soon as a global function is used, the program that contains that function is loaded into memory as an open file. And since it's an active loaded file, it seems to lock out re-saving the file, as if it's trying to create a new file but can't delete the old one first since it's open.
PxPlus v13.10 on Linux RedHat 5.11 with WindX through *nthost/*ntslave
PxPlus v13.10 on Linux RedHat 5.11 with WindX through *nthost/*ntslave
202
Programming / Re: Program Caching
« on: December 16, 2019, 09:49:41 AM »
We've set up a separate program to contain all of our global functions, in anticipation of making changes in the future without having to modify our standard startup program. Now that I want to make a change, I can't save the program under the same name; I get Error#0: Record/file busy.
Is there a way around this? Or do I need to have everyone get to a point of not using any of the global functions?
Thanks!
Is there a way around this? Or do I need to have everyone get to a point of not using any of the global functions?
Thanks!
203
Nomads / Re: File Maint with Main window data fields and Folder
« on: November 27, 2019, 12:14:48 PM »
When we finally upgrade to that in early 2020, we'll look into it. For now, I'll work on the code review.
204
Nomads / Re: File Maint with Main window data fields and Folder
« on: November 27, 2019, 11:39:23 AM »
It's a single-key file, and there were no changes that affect that, that I am aware of. I'm wondering if it's something to do with "splitting" fields in the FIELDS group between the main window and the tab. That still wouldn't explain why tabs other than the first work fine when they're the ones displayed on a FIND_REC.
I'll review things again, to see if there's something I missed.
I'll review things again, to see if there's something I missed.
205
Nomads / Re: File Maint with Main window data fields and Folder
« on: November 26, 2019, 05:00:56 PM »
Yes, it was originally created as a Generated F/M, but all non-key fields were on the folder's tabs. It's also a Custom Type F/M program, which allows us to control a number of the processes.
That said, we've done a bit of tweaking on the originals, due to new fields being added to the file. The original first tab (.1) had a new first tab (.0) inserted before it, so it became the second tab. Others were also added along the way, getting inserted and shuffled. The inter-tab "Folder_Tab_n" elements have been added/deleted/updated accordingly.
We're now eliminating the first tab (.0), using another tab (.3) as the new first tab. The folder object has the desired sequence of tabs (.3, .1, .2, .4, .9), and the Folder_Tab_n elements work. It's just getting that first tab's objects to be enabled when retrieving a record that's weird. Again, having another tab active when retrieving the record has that tab's objects enabled, and switching to the first (.3) will subsequently work.
That said, we've done a bit of tweaking on the originals, due to new fields being added to the file. The original first tab (.1) had a new first tab (.0) inserted before it, so it became the second tab. Others were also added along the way, getting inserted and shuffled. The inter-tab "Folder_Tab_n" elements have been added/deleted/updated accordingly.
We're now eliminating the first tab (.0), using another tab (.3) as the new first tab. The folder object has the desired sequence of tabs (.3, .1, .2, .4, .9), and the Folder_Tab_n elements work. It's just getting that first tab's objects to be enabled when retrieving a record that's weird. Again, having another tab active when retrieving the record has that tab's objects enabled, and switching to the first (.3) will subsequently work.
206
Nomads / File Maint with Main window data fields and Folder
« on: November 26, 2019, 04:30:01 PM »
We're moving some fields from a tab in a folder to the main part of a F/M window, to eliminate that tab. When was bring up a record, the tab key moves through the fields, then to the tab header, but for the first tab in the folder, all of the fields are disabled. Switching to another tab and then back again enables them properly. If a different tab is displayed when the record is retrieved, all of the fields are enabled properly, and switching to the first tab also enables those.
I can't find any notable differences between the tab panel headers. Is there something I'm missing to get that first tab enabled when retrieveing a record?
Thanks, all!
PxPlus v13.10 on Linux RedHat 5 with WindX
I can't find any notable differences between the tab panel headers. Is there something I'm missing to get that first tab enabled when retrieveing a record?
Thanks, all!
PxPlus v13.10 on Linux RedHat 5 with WindX
207
Programming / Memory File Speed
« on: October 24, 2019, 11:32:25 AM »
Does anyone know whether it would be faster to PURGE a memory file or CLOSE/reOPEN it? There are 2 keys and relatively few records (<50).
Thanks!
Thanks!
208
Programming / Re: incorrect evaluation
« on: October 16, 2019, 10:06:11 AM »
The 'AND' and 'OR' operators have the same precedence level, so they are evaluated left-to-right. In this case, it essentially works out to be:
Code: [Select]
if (1 or 0) and 0 then print "*"
209
Nomads / Re: Hotlink Logic
« on: October 04, 2019, 10:17:30 AM »
According to the documentation, the 'ColumnClicked property is only available on a ListView listbox. If it's available for other listboxes as well, it would help to have the documentation updated. (Any other properties for any of the controls would be good to have, too.)
210
Programming / Extended File Info from open Directory
« on: October 02, 2019, 10:48:49 AM »
I recall seeing (somewhere) a Directory being opened with certain options, and the READ providing more than simply the name. Does anyone know what that might be?
We're currently using RedHat Linux 5.
Thanks!
We're currently using RedHat Linux 5.
Thanks!