

Is there some other way to disable this file or hide the "standard" custom toolbar buttons?; SciTE4AutoHotkey global configuration file
;
; Do NOT edit this file, use UserToolbar.properties instead!
;
No big deal, just FYI, I have followed those instructions, but I still get "Edit global toolbar properties" in toolbar context menu.fincs wrote:Download the hotfix I've just released (Right click on Toolbar > Check for updates...), and create an empty $NODEFTOOLBAR file in your SciTE user folder.
My bad, I didn't read the request correctly and thought it was to disable the edit option for that file.fincs wrote:The update doesn't remove the 'Edit global toolbar properties' command, it merely allows you to create a $NODEFTOOLBAR file in order to disable the processing of the global toolbar properties.
Why isn't it a normal property, like tillagoto.enable? Or a directive in the user toolbar properties?fincs wrote:... create an empty $NODEFTOOLBAR file in your SciTE user folder.
So with $NODEFTOOLBAR, not only does the menu item not "Edit" the file as indicated, but the file itself does nothing. So it's both misleading and useless.The update doesn't remove the 'Edit global toolbar properties' command
Touché!lexikos wrote:So it's both misleading and useless.
Toolbar configuration processing is done before the director interface is set up. Moreover, if the director interface fails to initialize, the setting would be ignored.lexikos wrote:Why isn't it a normal property, like tillagoto.enable?
I considered this, however it would have been more complex to implement. Both the global and the local property files are internally merged before processing, and the internal toolbar button structure is initialized with some predefined buttons that should not be removeable.lexikos wrote:Or a directive in the user toolbar properties?
I decided against hiding items related to editing global properties because people may want to read them as reference. However I'll rename the commands to 'View'.lexikos wrote:So with $NODEFTOOLBAR, not only does the menu item not "Edit" the file as indicated, but the file itself does nothing. So it's both misleading and useless.
I am glad you chose view rather than hide, as I often use the global properties as hints for what I can put in my user properties. Thank you.fincs wrote: I decided against hiding items related to editing global properties because people may want to read them as reference. However I'll rename the commands to 'View'.
Users browsing this forum: No registered users and 6 guests