the whole suite menus/action use dispatch framework
this is useful when one want to disable some UI commands
especially, it is said :
The dispatch framework works with the design pattern chain of responsibility
The disable commands implementation is the first chain member and can therefore work as a wall for all disabled commands. They are not be sent to the next chain member, and disappear.
applying this to "Insert" command works for menu entries (insert > sheet or right click on a sheet tab) - see given macro code
but, the Insert is still available
- by clicking the green + button
- by clicking empty space near sheet tabs
--> these 2 functionality should respect the dispatch framework
the macro to test this - answer yes/No wether you want to disable/enable the Insert sheet command
conf = getConfigSetting("/org.openoffice.Office.Commands/Execute/Disabled" ,true)
message = "do you want to DISABLE ""insert sheet"" command ?"
response = msgBox(message, 32 + 4, "Question")
value = (response = 6)
if state then
spliter = split(url,"?")
nom = spliter(0)
if not conf.hasByName(nom) then
elem = conf.createInstanceWithArguments(array())
spliter = split(url,"?")
nom = spliter(0)
if conf.hasByName(nom) then
function getConfigSetting(target as string, forUpdate as boolean)
' retourne le noeud de config demandé
' exemple: aSettings = getConfigSetting( "/org.openoffice.Office.Common/Path/Current", false)
dim service as String ' nom du service d'acces à la configuration
dim aSettings, aConfigProvider
dim aParams(0) As new com.sun.star.beans.PropertyValue
if forUpdate then
service = "com.sun.star.configuration.ConfigurationUpdateAccess"
service = "com.sun.star.configuration.ConfigurationAccess"
aConfigProvider = createUnoService( "com.sun.star.configuration.ConfigurationProvider" )
aParams(0).Name = "nodepath"
aParams(0).Value = target
aSettings = aConfigProvider.createInstanceWithArguments(service, aParams() )
getConfigSetting = aSettings
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Dear bug submitter!
Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.
To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement
Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.
Nobody tested yet. Reopening
I can't get the macro to do anything for me. It asks if I want to disable the insert sheet command and I click yes, but I'm still able to insert sheet ANY method (insert - sheet, right click on sheet1 and do Insert Sheet..., Clicking Green +, or Empty Space)
Can you verify that your macro disables insert sheet in any way? I don't know the code so I can't verify that aspect but I want to confirm that we're on the same page before triaging the bug. Marking as NEEDINFO until you respond.
Thanks for your patience and apologies for the long delay.
i confirm the macro does do anythoing anymore
i'll have a look
i let you know
Created attachment 70382 [details]
a file with a correct macro
Please find an ods document with the macro inside (enable macros in security)
click the button to DISABLE (answer Yes) or ENABLE (answer No)
disapear in menu Insert
Right click on tab, the menu entry iss still there but inactive
the other described way are still available
Confirmed, quite strange :)
Marking as NEW and prioritizing:
Minor: Doesn't prevent high quality/professional work
Low: Very very few users would actually care about this - the number of users using macros is already low, one as specific as limiting the ability to make new sheets is probably less than 0.1% of users.
Leaving PrposedEasyHack as I don't think it'd be that difficult to fix.
Thanks for your patience and the test document
In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval.
Thank you and apologies for the noise
Migrating Whiteboard tags to Keywords: (needsDevEval)
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!