Just one more thing to add Ron<g>...
If you save the "for one workbook" version as an add-in (XLAM) then it
becomes a "for all workbooks" version and a button does not have to be
manually added to the QAT. This seems like the way to go in the "for all
workbooks" scenario since, I assume, these are utility macros and the user
doesn't need easy access to the workbook with the macros itself.
One thing that bothers me a bit is that, during the beta, MS (Jensen
Harris?) made it very clear they did not want developers sticking their
buttons on the QAT. That was supposed to up to users to do if they want.
But it so easy to do it is tempting. Plus I haven't seen anything outside
of the beta discouraging it except maybe Patrick Schmid's 'style' paper
which is not official.
--
Jim
| Hi
|
| > The "for all workbooks" version is saved in the Excel.qat file so that
would
| > have to be manually added by each user I believe. Is that correct?
|
| Correct Jim, I will make that more clear on the website.
|
|
| > I find that the "for one workbook" version is saved with the file, so I
was
| > wrong about that.
|
|
http://www.rondebruin.nl/qat2.htm
| With this example we can send the file to other users and they can use the
button in the QAT
| to open the menu.
|
| Btw: Useful thread Jim
|
|
|
| --
|
| Regards Ron de Bruin
|
http://www.rondebruin.nl/tips.htm
|
|
| > Ron-
| >
| > I find that the "for one workbook" version is saved with the file, so I
was
| > wrong about that.
| >
| > The "for all workbooks" version is saved in the Excel.qat file so that
would
| > have to be manually added by each user I believe. Is that correct?
| >
| > --
| > Jim
| > | > |> Bear in mind that the user has to manually add a button to the QAT
and
| > | > manually attach the macro to it.
| > |
| > |
| > | The button in the QAT is saved with file Jim as far as I test it on
| > different VPC's with O2007
| > | Do you see something different ?
| > |
| > |
| > | --
| > |
| > | Regards Ron de Bruin
| > |
http://www.rondebruin.nl/tips.htm
| > |
| > |
| > | > | >>>XML script
| > | >
| > | > You used that term a couple times, Michael. I believe it's an
oxymoron.
| > | > XML is not a script. It is a markup language for describing
structured
| > | > data. A fancy table, if you will. It is not inherently executable
as a
| > | > script is, although a program can read it an do anything it wants
with
| > it.
| > | >
| > | >>>create a button to utilise something like Rons 'MenuMaker'
| > | >
| > | > Bear in mind that the user has to manually add a button to the QAT
and
| > | > manually attach the macro to it. This is somewhat differently than
a
| > ribbon
| > | > tab appearing automatically when a user opens an Excel workbook or
| > add-in.
| > | > So I'd use this approach for making my Personal.xls macros easier
for me
| > to
| > | > get to but, for an application that's going to be distributed to
users,
| > I
| > | > think you have to go the RibbonX route.
| > | >
| > | > --
| > | > Jim
message
| > | > | > | > | Ron / Bob / Jim,
| > | > |
| > | > | Many thanks for all of your advice & comments, as usual its spot
on
| > | > | and you have addressed the questions l was going to raise as a
result
| > | > | of 'playing around' with XL2007menu customisation.
| > | > |
| > | > | I have Visio 'somewhere' and will give that a try
| > | > |
| > | > | Here are some of my comments / observations after 'playing
around'. If
| > | > | l have got anything wrong or if you have any comments to add l
would
| > | > | be gratefull for your reply.
| > | > |
| > | > | I have now got a few ' XML templates ' that l can use to satisfy
the
| > | > | most frequently menu layouts l use. In my opininion they are not
as
| > | > | user friendly / efficient as the XL2003 & previous versions
because
| > | > | they either require more clicks to access (ie in previous versions
ABC
| > | > | Ltd could be a command bar item and upon clicking the user could
| > | > | immediately acces their macros via a dropdown/popup.) or they are
not
| > | > | so pleasing to the eye. (this is a matter of opinion, if you like
| > | > | XL2007 you might think them attractive!)
| > | > |
| > | > | For presentation purposes l like the client to have their own menu
so
| > | > | in XL2007 l create a custom tab & group.( I assume l am correct in
| > | > | that you cannot have an 'On Action' attribute within Tab & Group)
I
| > | > | then have to add buttons to the custom group and have the
following
| > | > | choice:
| > | > |
| > | > | A) using XML script / callbacksto generate buttons / dropdowns
within
| > | > | the group. This is user friendly for the end user and requires the
| > | > | same number of clicks. The drawback being the amount of effort
| > | > | required by the developer who will need to learn XML if they are
not
| > | > | familiar with it.
| > | > |
| > | > | B) create a button to utilise something like Rons 'MenuMaker'.
This
| > | > | requires an additional click by the user. From a developers view
it
| > | > | involves a very few lines of XML script and everything can then be
| > | > | added to the menu from within the workbook
| > | > |
| > | > | I am also looking forward to somebody developing an application
that
| > | > | combines true XML editing and the features of the CustomUIEditor
| > | > |
| > | > | Regards
| > | > |
| > | > | Michael beckinsale
| > | > |
| > | >
| > | >
| >
| >
