|
|
Post by George on Sept 18, 2022 9:00:27 GMT -5
Robert: Yes, extremely messy. Every one of them is a separate primary command. A lot of them are boolean values (now to have multiple values). Every test or display of the value in code, macro etc. Needs altering.
Best I can suggest is to simply remove values like HEX from the Profile saving.
|
|
|
|
Post by Stefan on Sept 19, 2022 10:36:46 GMT -5
FWIW...
The easy way to make temporary profile changes is to LOCK the profile.
I agree with Robert that having the HEX ON/OFF setting in the profile is perhaps a bit harsh, given the profile applies to all files of that type. I too occasionally 'take a peek' at some Hex, but it isn't a huge issue for me subsequently because my profiles are typically LOCKED. So my HEX setting IS temporary and doesn't persist to other/all files of that type. In the rare case that I want to change a PROFILE setting permanently, it is no big deal to issue PROFILE UNLOCK, change the setting and then issue PROFILE LOCK. It means that a permanent change requires a very deliberate action, while my messing around with settings for individual files causes no lasting effects. BUT... maybe the idea about some (which?) setting to be also saved in STATE data is good. In the above example, when I save (and only when I save!) a file with particular settings, then that/those setting(s) remain in effect for subsequent visits to THAT particular file only. That would be a useful way of implementing Robert's the suggestion.
So settings like HEX remain in the profile, but they would also be recorded in the STATE file, IF (perhaps only if) their value at the point the file is saved differs from that in the profile. I assume that when a file is 'LOADED', the profile settings "apply" first, followed by the STATE settings. IF so, this suggestion should be relatively simple to realise (famous last words!)
I do not reckon a variety of different arguments for eg: HEX command to dictate what should happen is a good idea (KISS failure!) The LOCK facility of the profile already enables temporary changes.
The STATE concept is tailor made to retain changes for individual files. |
|
|
|
Post by Stefan on Sept 19, 2022 14:18:57 GMT -5
R,
Why not simply keep your profiles LOCKED at all times, UNLESS you wish to deliberately make a change that is intended to apply to ALL files of the same type?
I guess it depends how frequently you change your profiles. I find that once I've used a new profile (ie filetype) for a few days, the profile is as I want it. So I LOCK it to prevent inadvertent changes, by me or by loading a file with different characteristics which happens to have a wrong/misspelt file extension/type.
I think the issue stems from keeping profiles UNLOCKED.
But I do support the concept that STATE processing could "capture" a difference for a particular file and thus msintain it selectively.
|
|
|
|
Post by George on Sept 21, 2022 9:52:03 GMT -5
You guys realize that stuffing Profile option overrides into the STATE data will mean that StateLoad will now be expected to parse out all those options (about 35+ of them).
And that StateSave will have to do the opposite, somehow managing to figure out whether the current setting is the same as what's in the real Profile data, or whether it's a temporary override. And considering there's only one resident copy of a Profile variable, how does it know which value it is?
I agree with Stefan - LOCK your profiles, what we're trying to do here is exactly what LOCK/UNLOCK were designed for. Customizing profile data at an individual files level seems to me to be just a wee too much spoon-feeding of the "Hey! This is a neat idea" school. Yes there's some small 'need' for it, but really?
George
|
|
|
|
Post by Stefan on Sept 21, 2022 10:02:23 GMT -5
NO worries- locked profiles work great for me.
In fact, I came a cropper yesterday chasing my tail for hours because I create a new file type without locking the profile.
Some lines contained a backslash (\) followed by some more text.
Every time I saved the file, the data after the \ vanished on reload.
Quickly realised tey were never SAVEd.
Took ages to realise that I had accidentally turned on PRESERVE C !!!
|
|
