|
|
Post by Stefan on Apr 26, 2017 7:09:04 GMT -5
Observed using Windows 10 Pro Version 1607, 64-bit. and SPFLite Version 8.5.7027
The PROFILE Editor dialog cannot "undo" the effect of a previous "PROFILE USE xxxx" instruction. Blanking out of the PROFILE USE name field is not retained after <DONE> was clicked.
PROFILE RESET shows the default version of the profile but fails to save it. On re-opening the file the Profile shows as before (not reset).
Only way to "undo" this appears to be via the "PROFILE USE" primary command without an operand which, according to HELP, is not a valid command.
|
|
|
|
Post by George on Apr 26, 2017 14:09:27 GMT -5
To clear a USING, just do a PROF EDIT and blank the USING field. No, I will not pollute the PROF syntax with yet more operands to allow this with a command line version.
Also, please move to the latest 8.5.7110 version. There were problems corrected in Profile Edit, so it's not worth chasing until you're on the latest level.
George
|
|
|
|
Post by George on Apr 26, 2017 16:19:08 GMT -5
I don't understand. I have a profile for .INC (PowerBasic Include files) which has a USING (BAS) set.
When I edit an INC file, I get the normal colorize for BAS, and the PROF display shows USING (BAS)
Then I do a PROF EDIT INC and blank the USING field.
Edit the INC file again, the Profile just says INC and there is no colorize (since I don't have an INC.AUTO file)
Reverse it all, and colorize and PROF display all show the USING set up properly.
What am I to do? What you're describing just doesn't jive with what I'm seeing. Check your Profile LOCK value, maybe you're being caught out on that. (BTW, maybe we should never have supported LOCK, it's a royal PITA)
As to how USING works, when a Profile is being loaded, the first thing it does it to look at the USING value and if not blank, it swaps it in and starts the Profile load all over again. That's it.
George
|
|
|
|
Post by George on Apr 27, 2017 10:05:24 GMT -5
Robert: If you're having access problems, then you have some security setup getting in the way. I can Edit, Browse, View etc. etc. any of the INI files, profiles, SPFLite.INI etc. without problem.
And again, as I have said to you over and over, SPFLite does not Read, Write or in any other way access the INI files itself. ALL access is via the normal Windows API calls to handle INI files (which is goodness, since these APIs handle caching and other performance items).
George
|
|
