|
|
Post by George on Aug 19, 2023 11:26:37 GMT -5
MUEH: Maybe it doesn't say specifically (if it doesn't, I'll correct it) but the file/pathname should always be the last "word" in the command line. Other leading operands are processed and stripped out, whatever remains after that is assumed to be the file/path.
I'll look for the other problems. Thanks for confirming the -INSTANCE is back working at least partially.
George
[UPDATE]
EFT problem is found. One last place missed where it still referenced the "EDefault" table and not the "E"+instancename table.
[/UPDATE]
[UPDATE2]
Not clear on your 2nd problem. Here's what I've tried:
Start SPFLite from Cmd line - no operands
Load a file, leave SPFLite running
Start SPFLite again from the Cmd line with an operand of a different full-path filename, it loads ok into the existing session
Close it all down
Start SPFLite from the command line as another Instance
Load a file, leave SPFLite running
Start SPFLite again, same instance-name, with a different full-path filename, it loads OK into the existing Instance session.
Close it all down.
What am I missing?
[/UPDATE2]
|
|
|
|
Post by mueh on Aug 19, 2023 12:48:50 GMT -5
Hi George!
I played around and if i turn off "Only 1 SPFLite running" it works .
I assume you don't have it on to reproduce but you should have 2 Window instead of a Tab in existing window .
|
|
|
|
Post by George on Aug 19, 2023 13:18:20 GMT -5
MUEH: Thanks, good clue, I'll go chase.
Too many G.D. options!
George
[UPDATE]
OK, found, I'll post a new Beta tomorrow.
[/UPDATE]
|
|
|
|
Post by Robert on Aug 22, 2023 13:56:14 GMT -5
I have a minor concern about the new AUTONAME feature. You define a value of NONE to mean that the AUTONAME takes the standard name for this file, so that a profile of BAS would have a standard AUTO name of BAS.AUTO.
Because of this, I feel that NONE is not a good choice for this value. We have already established the keyword STD to mean "standard". For instance, there is (Pen/STD) and LOCATE STD. Using a value of AUTONAME NONE seems to suggest that there is NO auto-file at all, rather than being the standard one. To me that makes NONE kind of misleading.
I believe the correct terminology here should be AUTONAME STD rather than AUTONAME NONE.
R
===> One more thing ...
If you were crazy enough to have a file with an actual type of STD, like ABCD.STD, then its "standard" name would already be STD, so you'd be ok. If you had a file called ABCD.XYZ and you wanted that to have an auto file of STD and the STD was a real auto name, you'd be out of luck. Your only recourse would be to make the AUTO name something else, like XSTD.AUTO.
But then, if you were going around with actual profiles named NONE or STD you are way overdue for the funny farm anyway, so you are already beyond my help :-))
===> Oh yeah, one other thing ...
There might a use for NONE if you wanted to say that there was NO auto-file at all. Maybe if you did have an auto file but for some reason you didn't want to use it (temporarily)? I am not really asking for this or advocating it, but if you used NONE as a value, that's what it should be used for, not what you're doing now.
|
|
|
|
Post by George on Aug 22, 2023 15:36:24 GMT -5
Robert: I chose NONE because in the PROF EDIT dialogue, we have SUBCMD, SUBARG, EMACRO, IMACRO, XFORM, and now we add AUTONAME.
It just looked weird when all those others saying NONE and AUTONAME being different, just looked odd.
Perhaps you may be right, but this is all about 'appearance', and STD, although used, is not as common as NONE for default values. I doubt seriously if NONE would be confusing to anybody. It stays.
(And BTW, I'm not keen at this point on doing the code changes, revising documentation again, including recreating screen shots, etc. to do this)
George
|
|
|
|
Post by Robert on Aug 22, 2023 16:32:37 GMT -5
Understand the lack of enthusiasm to change things once they are 'done'. I would just point out that SUBCMD, SUBARG, EMACRO, IMACRO and XFORM do not have a "standard" setting. When they say NONE it means that their function is not present. With AUTONAME, NONE does not mean there is no function; it means there is no overriding name.
Any time you are inconsistent, someone will be confused. Don't doubt it. But, I have no heart to push on this.
I know how you dislike pre-documentation (much less, post-documentation), but if we knew where you were going, some of these conflicts could have been avoided. I didn't even know you were making an AUTONAME profile option until this morning.
R
|
|
|
|
Post by George on Aug 23, 2023 8:40:17 GMT -5
Robert: Inconsistent? No, I would find STD much more confusing.
Odd, you say "it means there is no overriding name" - isn't that just what NONE means?
Also, asking for comments on every small change like whether to use NONE or something else, waiting for ANY response, and then discussing the various merits before doing the change and updating Doc. etc. would effectively slow changes to a crawl. You well know asking the forum for input on anything like that elicits complete silence.
AUTONAME was created and first mentioned back at the end of June, it has hardly been just introduced.
George
|
|
|
|
Post by mueh on Aug 23, 2023 13:00:54 GMT -5
Hi George!
If you issue f.e E and V as FM Line cmd's before enter all files are opened in mode of first cmd .
No problem in 23169 but fails in 23234 .
Thanks
|
|
|
|
Post by George on Aug 23, 2023 14:03:13 GMT -5
MUEH: Bugs never stop do they. I'll track it down.
George
|
|
|
|
Post by Robert on Aug 23, 2023 15:25:31 GMT -5
AUTONAME was mentioned and introduced in June? It's not in 23.169 and not in the documentation. Where is it? I never heard of it until yesterday. Maybe it's in your betas, but I don't use them. Earlier betas were unreliable, as I had reported, so perhaps it's "hiding in plain sight". Even so, betas don't come with documentation changes, so again I never heard of it.
I am less interested in you asking the forum than in you asking me. Adding an entirely new feature with a new name is not what I would call a minor little change. In addition to never hearing of it, I have no idea what it does, not exactly.
There was a time that you wanted my advice, but I am uncertain if that is still true. You ought to let me know where we stand. I wouldn't want to slow things to a crawl.
R
|
|
|
|
Post by George on Aug 24, 2023 9:26:34 GMT -5
Robert: Please, it was a trivial change to add an easy to justify small enhancement. I didn't think it warranted discussion before adding it.
As to your advice, its always been valuable. But if you do not want to participate in testing the Beta's, that's your call. But if you wait till a full release comes out and only then send in your comments and suggestions, do you really expect me to go back in and tweak things around to incorporate them? I do wish you would reconsider your participation.
You say Beta's are unreliable.
They're Beta's, they're not intended to be perfect and without bugs, if they were they'd be a full release. I don't release a Beta that I am not already using as my 'production' release. I can't recall a Beta with a bug so bad as to harm data (If I'm wrong, blame my memory). I even use my test versions (pre-Beta stage) as my normal SPFLite version and I've never been 'hurt'.
Users who help test are invaluable, there's simply no way I (or any other single person) could test all of SPFLite's functions in combination with all the various configuration options.
Beta documentation - Yes, it's very simple and minimal. I'm NOT going to try and maintain the normal Doc. in step with every modification to the Beta and publish it along with the Beta. Doing the Doc. is a major chore; doing repeated revisions as tweaks are made to the Beta is not something I'll undertake.
Besides, I can hardly expect Beta testers to plow through the 900+ page Doc. scanning for what's changed, so I'd STILL have to provide the short, quickie version that I do now.
George
|
|
|
|
Post by mueh on Aug 29, 2023 10:04:58 GMT -5
George:
Used EFT entry
.bat = prof,mode view
but when file is selected in FM it's opened in EDIT mode . Can change it now with MODE VIEW .
Did i missunderstand the override in EFT entry ?
Thanks for 23239 .
|
|
|
|
Post by George on Aug 29, 2023 10:09:15 GMT -5
MUEH: What you did was correct, let me chase it.
George
[UPDATE]
OK, newer Beta to correct the error. Boy! That MODE handling gets quite tricky. That was all working fine, but another fix 'broke' it.
[/UPDATE]
|
|
|
|
Post by Robert on Aug 29, 2023 17:14:16 GMT -5
I have a 16,000+ line macro file, which defines Unicode characters that I use, and I don't want to modify this file unless I'm really sure I want it changed. It's hard to reload the data from Unicode.org and recreate it, so I don't want to accidentally damage this file.
My EFT for this is,
UNICODE*.MACRO = BAS, MODE VIEW
Sure enough, the file is opened in View mode.
A PROFILE display shows,
==EFT> UNICODE*.MACRO = BAS, MODE VIEW
and there is a 'modified profile item' of <MODE VIEW> just after the MINLEN item.
It all seems to work correctly. Very cool, George
Glad you picked up the MODE idea, this is very useful. We now can protect important files without having to always remember to open them as view/browse. Now, it happens automatically.
R
|
|
|
|
Post by mueh on Aug 30, 2023 2:19:22 GMT -5
George:
Tested now AUTONAME ZJCL cmd f.e for Profile JCL . ( even specified in profile dialog or EFT override)
It appears that AUTO file used is always the profille name regardless what valid AUTONAME file is specified .
if i rename profile.AUTO (JCL.AUTO) no colorization takes place .
Thanks for 23241
|
|
