|
|
Post by Stefan on Sept 15, 2022 6:23:29 GMT -5
Hi George,
Running on Version 2.6.22217
I trying to extract the Profile's WORD string without joy.
In the process, I note that Get_Profile$ does not accept the following arguments: NAME RC=8 Unknown Command: NAME
MASK RC=8 Unknown Command: MASK
SCROLL RC=8 Unknown Command: SCROLL WORD RC=8 Unknown Command: WORD and complains about COLS RC=8 COLS command not supported in Macro mode
Run this simple macro to see for yourself:
I appreciate that, especially with EFT in the works and the recent removal of QUERY, the access to PROFILE values is perhaps a bit "work-in-progress" and fragmented at the moment. Some settings/values reported bythe PROFILE command can be obtained via Get_Profile$(...), others only via <Command> ? syntax, some via both approaches, and some not at all.
Assuming the documentation is correct, Get_Profile$(...) is clearly missing some code for NAME and WORD, and one might argue that COLS and SCROLL should at least report the basics, eg: ON/OFF or HALF/PAGE/etc.
It would be useful too if arguments like MARK, MASK and TABS were to return the string/line you can see on the PROFILE display (perhaps via MARKLINE, MASKLINE, TABSLINE arguments).
This would enable a macro to determine where the current tabs are set, etc.
|
|
|
|
Post by Stefan on Sept 16, 2022 6:52:17 GMT -5
R, Thought I replied to this - obviously did't hit <post>! I'll have a go at it. On Grandpa duty this weekend so wil probably be a few days until you see anything. |
|
|
|
Post by Stefan on Sept 23, 2022 8:06:43 GMT -5
OK, given Robert's invitation, I took a closer look at all aspects of PROFILE settings, including:
- The various ways a human or a macro can interrogate or change a setting
- What settings were missing or extraneous in the access methods - How consistenly information was reported by the various ways, to humans or macros
- Any peculiarities within the processes - Documentation irregularities
I must say that since George adding a '?' argument to most of the primary commands, the implementation is actually very tidy indeed.
As Robert requested, the data discovery takes tabular form. The table contains one row for each Profile setting, presented in functional groups rather than alphabetically, so related settings appear together.
Horizontally the data is divided into the following sections: - Profile Entries in CFG file
- The results from a PROFILE command, e.g. =PROF> lines - The primary commands that deal with each profile setting - The GET_PROFILE$(...) macro function - The FM CONFIG Profile Edit Dialog Panel
The attached files provide the table with subsequent comments and possible bug listings in several viewing formats:
REPORT.htm (198.14 KB) A single web page, view with any browser
REPORT.csv (12.48 KB) Straight forward CSV file, no highlighting, very hard to read!
See part 2 below for a 'purely within SPFLITE' version of the report.
|
|
|
|
Post by Stefan on Sept 23, 2022 8:08:00 GMT -5
This is part 2 of the previous post
I also have a version of the results entirely created within SPFlite, complete with highlighting, colouring support, frames etc.
The build process used some SPFLite features in very unusual ways, which in itself unearthed the odd bug here or there (and even some instability and crashes which I have still to diagnose further).
To view this properly, you'll need my colour scheme and the presence of the RASTER font (distributed with SPFLite)
If you would like to have a look, you will need the files within this archive:
The CFG file provides the appropriate environment (assuming you have the RASTER font already). Just rename your existing CFG temporarily and use the one in the archive, and copy the AUTO and MACRO files to their respective folders before loading the REPORT.TBL file.
|
|
|
|
Post by Stefan on Sept 23, 2022 8:22:54 GMT -5
Oh, thank you for the flowers.
I had quite a lot of fun - and it was raining outside anyway.
|
|
|
|
Post by Stefan on Sept 23, 2022 17:19:48 GMT -5
R, GMT. I'm in the UK, half way between London and Brighton on the south coast. Your post is showing as "8 hours ago" and my watch says 23.20 at the moment so I'm about 5-6ish hours ahead of you.
|
|
|
|
Post by Stefan on Sept 24, 2022 11:11:55 GMT -5
AHh yes - we're still on SUMMER time until some weekend in October (I think).
Who cares? I'm retired and my time is (mostly) my own.
Although I have to be careful at home.
It drives Cath crazy because she's still working and married to a guy who doesn't know (or care) what day it is much of the time.
|
|
