We recently decided to change the tooltip text on one of our buttons to
something else. I wasn't suprised (more dissapointed) to find out that
this is what happens:
We updated our customers so they would receive the correct tooltip
text. After performing the update, the Commandbars displays this
message:
"Due to a software update the toolbar '<toolbarname>' has
changed. Would you like to reset your customized toolbar and load the
new one?"
If the user selects 'no' then the tooltip text is not updated.
If the user seletcs 'yes' then any customizations they have made to the
toolbar (moving buttons, hiding buttons, etc.) are reverted.
Is it just me, or does this seem a bit silly?
Unless I'm missing something, it seems like this would be the case:
1. Make sure you have thought through your tooltip text very carefully.
Make sure there are no typos, etc. If you ever have to give a customer
an update, any time they have spent doing customizations is
waisted.
2. Make sure you have thought of every possible functionality that your
application will perform. Even if you don't have the functionality
built before releasing the product, still build the buttons in. You may
have 100 extra buttons that don't do anything when clicked, but they
will be there later if you need them. This way, if you decide to add
code to the buttons, you can just turn the visibility on rather than
have all of the customer's preferences whiped out. If you decide to add
a new button later, the same thing happens as when you change the
tooltip text: Bye Bye customized toolbar.
I've been whining to CodeJock for 2 years about the lack of dynamic
buttons/docking panes. There has to be someone else out there that
builds dynamic/scalable applications. Has anyone been able to
accomplish these tasks using the CodeJock controls? I'm finding it
difficult.
|