|
Post by TheFeDuke on Mar 7, 2016 10:19:00 GMT -5
I guess that because my %UserProfile% is too long, the actual filename and extension of the .INI file is obscured in the 'INI File is:' display box of the 'SPFLite Global Options' dialog window. The field is left justified. If it were right justified, much like the 'Target:' box of the Shortcut Properties dialog box, that important part would be visible. Alternatively, if the 'Cancel' and 'Done' boxes were side-by-side instead of up-and-down there would be more room to display the whole field. My requested priority on this is zero, unless you like the idea.
Related to .INI files, I plead guilty to giving in to curiosity and experimenting with the contents and will share my observations. I found two places where I could insert free-form comments that appear not to interfere with .INI file processing by SPFLite and that survive updates both by regular activity and the use of the 'options' command. I can display any such documentation using the FINDSTR batch command. I am OK with that, but seek your blessing/comments/cautions on such practices. Here are my hacks. They can be placed after the 'Build=' statement between the [System] and [Manager] tags. I also added a [Comment] tag and free-form text at the very end after [Mouse] and its keyword with no ill effects. Interesting!
So, naturally, I thought of the 'Comment:' box of the Shortcut Properties and room for a 'Comment' tab just crying to be filled in the 'SPFLite Global Options' dialog window using the latter method to title a new tab. User customized comments in INI! That also demands zero priority unless you are inspired by such an idea.
|
|
|
Post by George on Mar 7, 2016 11:30:49 GMT -5
John: My normal instant reaction is to say that any user direct alteration of the INI file is done on a 'user beware' basic, and I'd rather they simply stay out of the INI file.
Most of the settings in there are quite obvious and I hear all the time from users who say "Why shouldn't I simply alter these myself, it's only a text file". For the majority of items, that's OK, but there are some which aren't obvious and a) I don't feel like documenting them and b) I don't want to be involved when something goes wrong.
Given all that, if you want to add comments as entire new [....] blocks, feel free. SPFLite will not even see or know about them. I don't process the INI files directly in the program, I use the normal Windows API to manipulate the values. And I never enumerate the sections, I have no need to, so I won't see any new additional ones.
George
|
|