Re: Turning Bubble Help for a Form on and off
A bit late into this discussion, but what about the exceptions? I mean, to my thinking, it would be rare that someone would want ALL the bubblehelp turned off on a form. I have used bubblehelp as an aid to first time users of an application and also as part of the information of a button's or field's function. The latter I would not want the user to turn off normally, especially if the field or button is not going to be used very often. This is why I have a preferences form in which logical fields are placed that indicate various bubblehelp that can be turned off--but only the ones that I have actually scripted to do this on each form, leaving the ones wanted to be permanent alone....and yes it can be a whole lot of extra script but all are so similar that it is not that hard to incorporate--just tedious. I also do this for warning dialogs--some to remain on and others that can be turned off by the user via the preferences form.
I suppose Selwyn's script could be modified somewhat to accommodate this also...sort of like how you can leave some windows open when closing all the rest during a backup routine. Some crlf list perhaps of the fields wanted to still have the bubblehelp.
Not as generic I guess as when you would simply use the function to turn off all the bubblehelp.
Just thought I'd throw out the idea / exception.
A bit late into this discussion, but what about the exceptions? I mean, to my thinking, it would be rare that someone would want ALL the bubblehelp turned off on a form. I have used bubblehelp as an aid to first time users of an application and also as part of the information of a button's or field's function. The latter I would not want the user to turn off normally, especially if the field or button is not going to be used very often. This is why I have a preferences form in which logical fields are placed that indicate various bubblehelp that can be turned off--but only the ones that I have actually scripted to do this on each form, leaving the ones wanted to be permanent alone....and yes it can be a whole lot of extra script but all are so similar that it is not that hard to incorporate--just tedious. I also do this for warning dialogs--some to remain on and others that can be turned off by the user via the preferences form.
I suppose Selwyn's script could be modified somewhat to accommodate this also...sort of like how you can leave some windows open when closing all the rest during a backup routine. Some crlf list perhaps of the fields wanted to still have the bubblehelp.
Not as generic I guess as when you would simply use the function to turn off all the bubblehelp.
Just thought I'd throw out the idea / exception.
Comment