How can I write "tool-tips" for buttons in my database? 
Author Message
 How can I write "tool-tips" for buttons in my database?
Hi!

I was wondering if it was possible to write "tool tips" for any button
or part of a database.  That is an explanation that comes up in a
small box when the mouse is pointed over the button or specific area
of a database (i.e., to explain what data we can put in a box, for
example.  Or that this buttons does this, or the next thing to do is
... and explain what action should follow, just to give an idea).

TIA!



Sun, 22 Jun 2003 10:51:32 GMT
 How can I write "tool-tips" for buttons in my database?

Not as such, but you can build a help feature that is very similar using
the Status(Current Modifier Key) function.

Each button script would look something like this:

If Status(Current Modifier Key) = 1
Show Message
Else
(whatever the button is normally supposed to do)
End If

When the user holds down the shift key (or whichever modifier key you
elect to use) whilst clicking the button, the message appears without
invoking button's normal function.  You can have several messages in
succession in a single script, or even build a more elaborate system
whereby the user can move forward and backwards through the messages
(using separate scripts that call on each other).  If there are more than
a couple a messages, you should also include a cancel option.

When the shift key is not held down,  the normal function of the button is
invoked.

--
Bridget Eley


Quote:

> Hi!

> I was wondering if it was possible to write "tool tips" for any button
> or part of a database.  That is an explanation that comes up in a
> small box when the mouse is pointed over the button or specific area
> of a database (i.e., to explain what data we can put in a box, for
> example.  Or that this buttons does this, or the next thing to do is
> ... and explain what action should follow, just to give an idea).

> TIA!



Sun, 22 Jun 2003 15:43:52 GMT
 How can I write "tool-tips" for buttons in my database?
There may be a plugin that will assist in producing this effect,
but Filemaker itself will not.

Scott

Quote:
> Hi!

> I was wondering if it was possible to write "tool tips" for any button
> or part of a database.  That is an explanation that comes up in a
> small box when the mouse is pointed over the button or specific area
> of a database (i.e., to explain what data we can put in a box, for
> example.  Or that this buttons does this, or the next thing to do is
> ... and explain what action should follow, just to give an idea).

> TIA!



Sun, 22 Jun 2003 22:00:05 GMT
 How can I write "tool-tips" for buttons in my database?
<sigh> that's too bad.  It seems something else FMP can't do yet.
Below sounds great but you still have to prompt for an extra action
and then there is that extra step in between of pressing a modifier
key.  Tool tips would avoid the hassle (I had problem of trying to
remember what buttons did exactly what in a database I entered
yesterday after several months away from it.  And this is despite all
the extra time and effort I took to make it as user-friendly as
possible!  Messages all over, etc.)

You gave me an idea, though, on thinking this out a bit.  This is in
no way as efficient as a tool tip over a button would be but I have a
help button.  This "?" button would do better to just bring up a
message prompting user to press modifier key at the same time they
click on button to find out what any given button does.

This will make help instructions more precise because user will be
finding out what each button does rather than looking for its function
through a bunch of text.

Will this system below work with a right-mouse click instead of
pressing a modifier key, i.e., right-clicking over the button.  That
would be much, much more efficient for user.

TIA!

*****************************************


Quote:
>Not as such, but you can build a help feature that is very similar using
>the Status(Current Modifier Key) function.

>Each button script would look something like this:

>If Status(Current Modifier Key) = 1
>Show Message
>Else
>(whatever the button is normally supposed to do)
>End If

>When the user holds down the shift key (or whichever modifier key you
>elect to use) whilst clicking the button, the message appears without
>invoking button's normal function.  You can have several messages in
>succession in a single script, or even build a more elaborate system
>whereby the user can move forward and backwards through the messages
>(using separate scripts that call on each other).  If there are more than
>a couple a messages, you should also include a cancel option.

>When the shift key is not held down,  the normal function of the button is
>invoked.



Mon, 23 Jun 2003 04:33:52 GMT
 How can I write "tool-tips" for buttons in my database?
Tool tips are great when you are first learning an application but they
can quickly become invasive if you tend to hover a second too long.  I
usually end up turning them off if Preferences permit but that then
creates the hassle of having to turn them back on whenever you need to use
a set of buttons you are not totally familiar with.  

With using a modifier key in conjunction with a mouse click (and really,
how hard is that?), you have the best of both worlds.  Instant access and
non invasive messages.

A help button would obviously be the best way to alert users to the
presence of such a non-obvious in built help system.  You could make it
even more useful by scripting it to additionally offer the choice of
opening a help file (FileMaker Pro, pdf or plain text).  Some of us
actually do read the manual ;-)

One of the PC users/developers will have to address the right button
issue, but here again - the habit of using a modifier key in conjuntion
with a mouse click is not that difficult to learn!  Consistency is the
most important thing: if all buttons or icons are scripted to show a
message in this way, users should quickly fall into the habit of relying
on it.

--
Bridget Eley


Quote:

> <sigh> that's too bad.  It seems something else FMP can't do yet.
> Below sounds great but you still have to prompt for an extra action
> and then there is that extra step in between of pressing a modifier
> key.  Tool tips would avoid the hassle (I had problem of trying to
> remember what buttons did exactly what in a database I entered
> yesterday after several months away from it.  And this is despite all
> the extra time and effort I took to make it as user-friendly as
> possible!  Messages all over, etc.)
> You gave me an idea, though, on thinking this out a bit.  This is in
> no way as efficient as a tool tip over a button would be but I have a
> help button.  This "?" button would do better to just bring up a
> message prompting user to press modifier key at the same time they
> click on button to find out what any given button does.

A general help button is a great way to alert users to the presence of an
inbuilt help system.  
Quote:

> This will make help instructions more precise because user will be
> finding out what each button does rather than looking for its function
> through a bunch of text.

> Will this system below work with a right-mouse click instead of
> pressing a modifier key, i.e., right-clicking over the button.  That
> would be much, much more efficient for user.

> TIA!

> *****************************************


> >Not as such, but you can build a help feature that is very similar using
> >the Status(Current Modifier Key) function.

> >Each button script would look something like this:

> >If Status(Current Modifier Key) = 1
> >Show Message
> >Else
> >(whatever the button is normally supposed to do)
> >End If

> >When the user holds down the shift key (or whichever modifier key you
> >elect to use) whilst clicking the button, the message appears without
> >invoking button's normal function.  You can have several messages in
> >succession in a single script, or even build a more elaborate system
> >whereby the user can move forward and backwards through the messages
> >(using separate scripts that call on each other).  If there are more than
> >a couple a messages, you should also include a cancel option.

> >When the shift key is not held down,  the normal function of the button is
> >invoked.



Mon, 23 Jun 2003 05:18:48 GMT
 How can I write "tool-tips" for buttons in my database?
No there's no recognition for right/left clicking, and right click on a
button is the same as a left. Aesthetically, I like your help button idea.
You can have a "toggle" type button that when clicked sets a "switch" field,
and all the other button's scripts check the status of the switch and ether
perform their script or pull up a help layout particular to that button. If
you want to do this graphically nice you can create three global container
fields; one holds a picture of help icon, an other a shaded or "selected"
picture of the icon, and the third container is the button that when clicked
sets it's contents between one and the other.

--

C. Alex Lorda


Quote:
> Tool tips are great when you are first learning an application but they
> can quickly become invasive if you tend to hover a second too long.  I
> usually end up turning them off if Preferences permit but that then
> creates the hassle of having to turn them back on whenever you need to use
> a set of buttons you are not totally familiar with.

> With using a modifier key in conjunction with a mouse click (and really,
> how hard is that?), you have the best of both worlds.  Instant access and
> non invasive messages.

> A help button would obviously be the best way to alert users to the
> presence of such a non-obvious in built help system.  You could make it
> even more useful by scripting it to additionally offer the choice of
> opening a help file (FileMaker Pro, pdf or plain text).  Some of us
> actually do read the manual ;-)

> One of the PC users/developers will have to address the right button
> issue, but here again - the habit of using a modifier key in conjuntion
> with a mouse click is not that difficult to learn!  Consistency is the
> most important thing: if all buttons or icons are scripted to show a
> message in this way, users should quickly fall into the habit of relying
> on it.

> --
> Bridget Eley



> > <sigh> that's too bad.  It seems something else FMP can't do yet.
> > Below sounds great but you still have to prompt for an extra action
> > and then there is that extra step in between of pressing a modifier
> > key.  Tool tips would avoid the hassle (I had problem of trying to
> > remember what buttons did exactly what in a database I entered
> > yesterday after several months away from it.  And this is despite all
> > the extra time and effort I took to make it as user-friendly as
> > possible!  Messages all over, etc.)

> > You gave me an idea, though, on thinking this out a bit.  This is in
> > no way as efficient as a tool tip over a button would be but I have a
> > help button.  This "?" button would do better to just bring up a
> > message prompting user to press modifier key at the same time they
> > click on button to find out what any given button does.

> A general help button is a great way to alert users to the presence of an
> inbuilt help system.

> > This will make help instructions more precise because user will be
> > finding out what each button does rather than looking for its function
> > through a bunch of text.

> > Will this system below work with a right-mouse click instead of
> > pressing a modifier key, i.e., right-clicking over the button.  That
> > would be much, much more efficient for user.

> > TIA!

> > *****************************************


> > >Not as such, but you can build a help feature that is very similar
using
> > >the Status(Current Modifier Key) function.

> > >Each button script would look something like this:

> > >If Status(Current Modifier Key) = 1
> > >Show Message
> > >Else
> > >(whatever the button is normally supposed to do)
> > >End If

> > >When the user holds down the shift key (or whichever modifier key you
> > >elect to use) whilst clicking the button, the message appears without
> > >invoking button's normal function.  You can have several messages in
> > >succession in a single script, or even build a more elaborate system
> > >whereby the user can move forward and backwards through the messages
> > >(using separate scripts that call on each other).  If there are more
than
> > >a couple a messages, you should also include a cancel option.

> > >When the shift key is not held down,  the normal function of the button
is
> > >invoked.



Mon, 23 Jun 2003 09:45:20 GMT
 How can I write "tool-tips" for buttons in my database?


Quote:
>Tool tips are great when you are first learning an application but they
>can quickly become invasive if you tend to hover a second too long.  I

I can foresee this being a problem in long term, you're right.

[snip]

Quote:
>With using a modifier key in conjunction with a mouse click (and really,
>how hard is that?), you have the best of both worlds.  Instant access and

CAN it be done.  It was suggested that a modifier key with a keyboard
key be used.  I'm not keen on this for this particular instance.  I
think a modifier key with a right-click would be most efficient.

Quote:
>A help button would obviously be the best way to alert users to the
>presence of such a non-obvious in built help system.  You could make it

This was my idea once the solution of using a modifier key was put
forth.  Since there are no tool tips, I thought that my help button (a
round button with a question mark) could be revised to perform the
function of being there to tell user to right click on button for
purpose of feature, etc.

Quote:
>even more useful by scripting it to additionally offer the choice of
>opening a help file (FileMaker Pro, pdf or plain text).  Some of us
>actually do read the manual ;-)

Now this, too, is an excellent idea.  Have the message re modifier
mouse click (if this function is permitted) and then underneath that
somehow, have option to open up a help file.

Thank you for great tips!!



Fri, 27 Jun 2003 05:11:39 GMT
 How can I write "tool-tips" for buttons in my database?

Quote:

> >With using a modifier key in conjunction with a mouse click (and really,
> >how hard is that?), you have the best of both worlds.  Instant access and

> CAN it be done.  It was suggested that a modifier key with a keyboard
> key be used.  I'm not keen on this for this particular instance.  I
> think a modifier key with a right-click would be most efficient.

The script is attached to a button so there is no need to use a keyboard
shortcut.  You click the button using the mouse while holding down the
modifier key.  C. Alex's response suggested that right clicking makes no
difference in this instance so pursuing that angle might be a lost cause.
I am a Mac specialist so right clicking is not an option ;-)

--
Bridget Eley



Fri, 27 Jun 2003 05:34:11 GMT
 How can I write "tool-tips" for buttons in my database?
I love this new trick.  Thank you.
--
FMP Junkie
"Freebasing FMP 24/7"



Quote:
> No there's no recognition for right/left clicking, and right click on a
> button is the same as a left. Aesthetically, I like your help button idea.
> You can have a "toggle" type button that when clicked sets a "switch"
field,
> and all the other button's scripts check the status of the switch and
ether
> perform their script or pull up a help layout particular to that button.
If
> you want to do this graphically nice you can create three global container
> fields; one holds a picture of help icon, an other a shaded or "selected"
> picture of the icon, and the third container is the button that when
clicked
> sets it's contents between one and the other.

> --

> C. Alex Lorda



> > Tool tips are great when you are first learning an application but they
> > can quickly become invasive if you tend to hover a second too long.  I
> > usually end up turning them off if Preferences permit but that then
> > creates the hassle of having to turn them back on whenever you need to
use
> > a set of buttons you are not totally familiar with.

> > With using a modifier key in conjunction with a mouse click (and really,
> > how hard is that?), you have the best of both worlds.  Instant access
and
> > non invasive messages.

> > A help button would obviously be the best way to alert users to the
> > presence of such a non-obvious in built help system.  You could make it
> > even more useful by scripting it to additionally offer the choice of
> > opening a help file (FileMaker Pro, pdf or plain text).  Some of us
> > actually do read the manual ;-)

> > One of the PC users/developers will have to address the right button
> > issue, but here again - the habit of using a modifier key in conjuntion
> > with a mouse click is not that difficult to learn!  Consistency is the
> > most important thing: if all buttons or icons are scripted to show a
> > message in this way, users should quickly fall into the habit of relying
> > on it.

> > --
> > Bridget Eley



> > > <sigh> that's too bad.  It seems something else FMP can't do yet.
> > > Below sounds great but you still have to prompt for an extra action
> > > and then there is that extra step in between of pressing a modifier
> > > key.  Tool tips would avoid the hassle (I had problem of trying to
> > > remember what buttons did exactly what in a database I entered
> > > yesterday after several months away from it.  And this is despite all
> > > the extra time and effort I took to make it as user-friendly as
> > > possible!  Messages all over, etc.)

> > > You gave me an idea, though, on thinking this out a bit.  This is in
> > > no way as efficient as a tool tip over a button would be but I have a
> > > help button.  This "?" button would do better to just bring up a
> > > message prompting user to press modifier key at the same time they
> > > click on button to find out what any given button does.

> > A general help button is a great way to alert users to the presence of
an
> > inbuilt help system.

> > > This will make help instructions more precise because user will be
> > > finding out what each button does rather than looking for its function
> > > through a bunch of text.

> > > Will this system below work with a right-mouse click instead of
> > > pressing a modifier key, i.e., right-clicking over the button.  That
> > > would be much, much more efficient for user.

> > > TIA!

> > > *****************************************


> > > >Not as such, but you can build a help feature that is very similar
> using
> > > >the Status(Current Modifier Key) function.

> > > >Each button script would look something like this:

> > > >If Status(Current Modifier Key) = 1
> > > >Show Message
> > > >Else
> > > >(whatever the button is normally supposed to do)
> > > >End If

> > > >When the user holds down the shift key (or whichever modifier key you
> > > >elect to use) whilst clicking the button, the message appears without
> > > >invoking button's normal function.  You can have several messages in
> > > >succession in a single script, or even build a more elaborate system
> > > >whereby the user can move forward and backwards through the messages
> > > >(using separate scripts that call on each other).  If there are more
> than
> > > >a couple a messages, you should also include a cancel option.

> > > >When the shift key is not held down,  the normal function of the
button
> is
> > > >invoked.



Fri, 27 Jun 2003 15:14:43 GMT
 How can I write "tool-tips" for buttons in my database?
You can kill a few birds with one stone. Let's say you have several buttons,
or even fields that could use some explaining to the end-user. You could
duplicate the layout (which will be the "help" layout), make all fields in
that layout not accessible, and create bold and bright balloon help boxes
with arrows pointing to what the balloon field is describing. In essence,
here's what would happen. The user would click a "help" button you design,
and it would actually switch over to the help layout with the balloon help
description boxes. On that layout (the "help" layout) create another button
called "end help" (or whatever), and it would go back to the original active
layout.

Just an idea.
Russ


Quote:
> Hi!

> I was wondering if it was possible to write "tool tips" for any button
> or part of a database.  That is an explanation that comes up in a
> small box when the mouse is pointed over the button or specific area
> of a database (i.e., to explain what data we can put in a box, for
> example.  Or that this buttons does this, or the next thing to do is
> ... and explain what action should follow, just to give an idea).

> TIA!



Sun, 29 Jun 2003 13:19:47 GMT
 How can I write "tool-tips" for buttons in my database?
This is a good idea.  Thank you.

*****************************************
On Wed, 10 Jan 2001 05:19:47 GMT, "News|MediaOne"

Quote:

>You can kill a few birds with one stone. Let's say you have several buttons,
>or even fields that could use some explaining to the end-user. You could
>duplicate the layout (which will be the "help" layout), make all fields in
>that layout not accessible, and create bold and bright balloon help boxes
>with arrows pointing to what the balloon field is describing. In essence,
>here's what would happen. The user would click a "help" button you design,
>and it would actually switch over to the help layout with the balloon help
>description boxes. On that layout (the "help" layout) create another button
>called "end help" (or whatever), and it would go back to the original active
>layout.

>Just an idea.
>Russ



>> Hi!

>> I was wondering if it was possible to write "tool tips" for any button
>> or part of a database.  That is an explanation that comes up in a
>> small box when the mouse is pointed over the button or specific area
>> of a database (i.e., to explain what data we can put in a box, for
>> example.  Or that this buttons does this, or the next thing to do is
>> ... and explain what action should follow, just to give an idea).

>> TIA!



Mon, 30 Jun 2003 03:17:54 GMT
 How can I write "tool-tips" for buttons in my database?
To be consistent, you would need to make a help layout for every major
layout in the solution - this would work for some solutions (small
solutions, few files, few layouts)  but could quickly and unnecessarily
bloat a larger solution, especially if there are a lot of graphical
objects on each layout (and the help solution Russ is suggesting would add
even more).  

Help systems are usually most useful during the early stages of using an
application and quickly become redundant.  This means a lot of permanent
extra overhead for only a limited period of utility.

--
Bridget Eley


Quote:

> This is a good idea.  Thank you.

> *****************************************
> On Wed, 10 Jan 2001 05:19:47 GMT, "News|MediaOne"

> >You can kill a few birds with one stone. Let's say you have several buttons,
> >or even fields that could use some explaining to the end-user. You could
> >duplicate the layout (which will be the "help" layout), make all fields in
> >that layout not accessible, and create bold and bright balloon help boxes
> >with arrows pointing to what the balloon field is describing. In essence,
> >here's what would happen. The user would click a "help" button you design,
> >and it would actually switch over to the help layout with the balloon help
> >description boxes. On that layout (the "help" layout) create another button
> >called "end help" (or whatever), and it would go back to the original active
> >layout.

> >Just an idea.
> >Russ



> >> Hi!

> >> I was wondering if it was possible to write "tool tips" for any button
> >> or part of a database.  That is an explanation that comes up in a
> >> small box when the mouse is pointed over the button or specific area
> >> of a database (i.e., to explain what data we can put in a box, for
> >> example.  Or that this buttons does this, or the next thing to do is
> >> ... and explain what action should follow, just to give an idea).

> >> TIA!



Mon, 30 Jun 2003 04:24:10 GMT
 How can I write "tool-tips" for buttons in my database?
There is a nice solution for building Help files.
FMP help builder.
You can create a complete help file that can be printed  if you want. It
looks a bit like the Windows or Mac help files.
You can create a small button beside the fields that would require more
instructions. When you click on the button, it takes you directly to the
spot in the helpfile concerning that specific help.

I tried the DEMO and it seemed to work pretty well

http://www.dwdataconcepts.com/



Quote:
> To be consistent, you would need to make a help layout for every major
> layout in the solution - this would work for some solutions (small
> solutions, few files, few layouts)  but could quickly and unnecessarily
> bloat a larger solution, especially if there are a lot of graphical
> objects on each layout (and the help solution Russ is suggesting would add
> even more).

> Help systems are usually most useful during the early stages of using an
> application and quickly become redundant.  This means a lot of permanent
> extra overhead for only a limited period of utility.

> --
> Bridget Eley



> > This is a good idea.  Thank you.

> > *****************************************
> > On Wed, 10 Jan 2001 05:19:47 GMT, "News|MediaOne"

> > >You can kill a few birds with one stone. Let's say you have several
buttons,
> > >or even fields that could use some explaining to the end-user. You
could
> > >duplicate the layout (which will be the "help" layout), make all fields
in
> > >that layout not accessible, and create bold and bright balloon help
boxes
> > >with arrows pointing to what the balloon field is describing. In
essence,
> > >here's what would happen. The user would click a "help" button you
design,
> > >and it would actually switch over to the help layout with the balloon
help
> > >description boxes. On that layout (the "help" layout) create another
button
> > >called "end help" (or whatever), and it would go back to the original
active
> > >layout.

> > >Just an idea.
> > >Russ



> > >> Hi!

> > >> I was wondering if it was possible to write "tool tips" for any
button
> > >> or part of a database.  That is an explanation that comes up in a
> > >> small box when the mouse is pointed over the button or specific area
> > >> of a database (i.e., to explain what data we can put in a box, for
> > >> example.  Or that this buttons does this, or the next thing to do is
> > >> ... and explain what action should follow, just to give an idea).

> > >> TIA!



Mon, 30 Jun 2003 05:48:32 GMT
 How can I write "tool-tips" for buttons in my database?
Dear Listeners:

Some while ago I pointed out here an option I use in all my solutions - ONE
button with a question mark in it, when clciked it shows a 1 line message:
"All fieldnames can be clicked for help."
Then I make each fieldname a button with a max. 4 line help message.
No cluttered screen, fast, easy to maintain, and it forces oneself to be
*very* succinct in giving help within 4 lines...

--

Met vriendelijke groet / Mit freundlichen Gruessen / With kind regards
Christoph Bouthillier
post (at) no-no-spamtekstotaal.com
Please remove "no-no-spam" when E-mailing me directly - Thanks
------


Quote:
> There is a nice solution for building Help files.
> FMP help builder.
> You can create a complete help file that can be printed  if you want. It
> looks a bit like the Windows or Mac help files.
> You can create a small button beside the fields that would require more
> instructions. When you click on the button, it takes you directly to the
> spot in the helpfile concerning that specific help.

> I tried the DEMO and it seemed to work pretty well

> http://www.dwdataconcepts.com/



> > To be consistent, you would need to make a help layout for every major
> > layout in the solution - this would work for some solutions (small
> > solutions, few files, few layouts)  but could quickly and unnecessarily
> > bloat a larger solution, especially if there are a lot of graphical
> > objects on each layout (and the help solution Russ is suggesting would
add
> > even more).

> > Help systems are usually most useful during the early stages of using an
> > application and quickly become redundant.  This means a lot of permanent
> > extra overhead for only a limited period of utility.

> > --
> > Bridget Eley



> > > This is a good idea.  Thank you.

> > > *****************************************
> > > On Wed, 10 Jan 2001 05:19:47 GMT, "News|MediaOne"

> > > >You can kill a few birds with one stone. Let's say you have several
> buttons,
> > > >or even fields that could use some explaining to the end-user. You
> could
> > > >duplicate the layout (which will be the "help" layout), make all
fields
> in
> > > >that layout not accessible, and create bold and bright balloon help
> boxes
> > > >with arrows pointing to what the balloon field is describing. In
> essence,
> > > >here's what would happen. The user would click a "help" button you
> design,
> > > >and it would actually switch over to the help layout with the balloon
> help
> > > >description boxes. On that layout (the "help" layout) create another
> button
> > > >called "end help" (or whatever), and it would go back to the original
> active
> > > >layout.

> > > >Just an idea.
> > > >Russ



> > > >> Hi!

> > > >> I was wondering if it was possible to write "tool tips" for any
> button
> > > >> or part of a database.  That is an explanation that comes up in a
> > > >> small box when the mouse is pointed over the button or specific
area
> > > >> of a database (i.e., to explain what data we can put in a box, for
> > > >> example.  Or that this buttons does this, or the next thing to do
is
> > > >> ... and explain what action should follow, just to give an idea).

> > > >> TIA!



Wed, 02 Jul 2003 06:41:00 GMT
 How can I write "tool-tips" for buttons in my database?
Using a script with a Status "if" statement, you could vreate a pop-up
window with a few lines describing what the object / area / field / button /
etc... is.  e.g...

If [Status(CurrentModifierKey) = 1]
      Show Message [The item you are looking at is yadda yadda...]
Else
   -- whatever the button would normally do...

End If

I use this a lot, and I also have a big dot with a question mark in it at
the same area on each layout that takes the user to a help file to give a
more detailed explaination of what things do, but this little pop-up usually
answers the general questions of what the heck an item is or does.

Also, the Modifier Key "1" is the shift button.  You could also use the alt
and control button to do other things too.  A very useful tool, IMHO.

--
FMP Junkie
"Freebasing FMP 24/7"


Quote:
> To be consistent, you would need to make a help layout for every major
> layout in the solution - this would work for some solutions (small
> solutions, few files, few layouts)  but could quickly and unnecessarily
> bloat a larger solution, especially if there are a lot of graphical
> objects on each layout (and the help solution Russ is suggesting would add
> even more).

> Help systems are usually most useful during the early stages of using an
> application and quickly become redundant.  This means a lot of permanent
> extra overhead for only a limited period of utility.

> --
> Bridget Eley



> > This is a good idea.  Thank you.

> > *****************************************
> > On Wed, 10 Jan 2001 05:19:47 GMT, "News|MediaOne"

> > >You can kill a few birds with one stone. Let's say you have several
buttons,
> > >or even fields that could use some explaining to the end-user. You
could
> > >duplicate the layout (which will be the "help" layout), make all fields
in
> > >that layout not accessible, and create bold and bright balloon help
boxes
> > >with arrows pointing to what the balloon field is describing. In
essence,
> > >here's what would happen. The user would click a "help" button you
design,
> > >and it would actually switch over to the help layout with the balloon
help
> > >description boxes. On that layout (the "help" layout) create another
button
> > >called "end help" (or whatever), and it would go back to the original
active
> > >layout.

> > >Just an idea.
> > >Russ



> > >> Hi!

> > >> I was wondering if it was possible to write "tool tips" for any
button
> > >> or part of a database.  That is an explanation that comes up in a
> > >> small box when the mouse is pointed over the button or specific area
> > >> of a database (i.e., to explain what data we can put in a box, for
> > >> example.  Or that this buttons does this, or the next thing to do is
> > >> ... and explain what action should follow, just to give an idea).

> > >> TIA!



Thu, 10 Jul 2003 07:37:48 GMT
 
 [ 15 post ] 

 Relevant Pages 

1. max of ("...","...","..")

2. "visual database tools" component

3. Tip: The truth about "local SQL"

4. OpenIngres "tech tip"

5. Curious, adding a "Print Threads" button

6. The "OLAP Services Processing Task" button

7. str.view() and button "cancel"

8. MRO problem with "invisible buttons"...?

9. Disabling the Win95 "X" button

10. Hide the Win95 Close "X" button

11. PDOXW 4.5: "Password" protecting buttons

12. Tab stops on "Borland buttons"


 
Powered by phpBB® Forum Software