how about a "toggle" as the last entry in each section that says "Help on
this param". Then show the help when it is clicked?

d

On Tue, Dec 2, 2008 at 8:36 AM, Dennis Brown <[EMAIL PROTECTED]> wrote:

> Herman,
> Thanks for the ideas.
>  more embedded below.
>
>  On Dec 2, 2008, at 5:38 AM, Herman wrote:
>
>  First: YES: I WOULD LOVE TO HAVE TOOLTIPS ADDED TO THE PARAM WINDOW.
> GREAT IDEA!
>
> You should make a suggestion on the feed back site. Since Amibroker, when
> hovering the cursor over the Param window, already pre-selects the
> individual parameters (you can see this because they change appearance when
> you move you cursor over the items) the information you need is already
> available inside AB. It might be a simple task for TJ to make this available
> through a Status().
>
>
> I noticed that the parameter name button changes appearance independent of
> the parameter button when the cursor is over it.  I thought that might be a
> clue for a way to differentiate a response.  If the name button could
> trigger a ParamTrigger() like response that could also be used for a popup.
>  Your suggestion of a Status() that indicated if the cursor is hovering over
> a parameter name or even if it was clicked could be a very.  Perhaps the
> status could be used in context so that it could follow an AFL parameter
> function and indicate if the cursor is currently over that parameter or the
> name was clicked.
>
> I will add a suggestion tomorrow (after any other suggestions come up).  I
> want to make sure I am suggesting something that is feasible so it does not
> just get rejected out of hand.
>
>
> As is, except for when you are using a GFX based Params (Buttons) systems,
> I don't think it is possible. You could however embed PopUpWindow() or
> ToolTip() in your custom Param functions so that they popup when the param
> is clicked - however this would be after the fact ;-) Unless you educate
> your user to only 'confirm' a parameter setting by clicking on it but not
> changing the parameter. This would require a certain skill.
>
> another way would be to have the Right mouse button popup an information
> window that is relevant to the current, or last, selected Param. Or pop up a
> custom menu with relevant information options.
>
>
> I know how to do this only for ParamTrigger() type parameters.  I can only
> detect user interactions for other types if the parameter is actually
> changed.
>
>
> I think it would be very useful to have this function. There are many among
> us who prefer coding to trading and who write code that is used by others. I
> myself spend lots of time and write hundreds of emails explaining how things
> work. Having Param Tooltips would save lots of time all around.
>
>
> It also makes it much easier to embed the documentation into the code so
> that it remains up to date with code changes and is handy as a reference
> during program operation.
>
>
> Best regards,
> herman
>
> Monday, December 1, 2008, 9:55:36 PM, you wrote:
>
> > Hello,
>
> > I have hundreds of parameters in my system (using Flexible
> > Parameters).  My trading mentor wants to learn and start playing with
> > my system in Jan (first time AB user).  I would like to be able to
> > have tooltip text pop up when he is over a parameter name in the
> > parameter window, or perhaps by left or right clicking on the
> > parameter name, have a commentary window or Gfx text box explaining
> > the parameter pop up in the chart.
>
> > I don't have a clue of how to make this happen, or if someone has a
> > different brilliant idea of how I can embed my parameter documentation
> > into the AFL program so the user can easily reference it.
>
> > Perhaps it is possible to trick the parameter name buttons to send
> > their name to somewhere that AFL could access somehow and pop up the
> > commentary.
>
> > I would appreciate any ideas.
>
> > Tomasz, If you can think of an AFL enhancement  that would make this
> > possible, I would love to suggest it.  I just don't know what
> > suggestion to make that would be practical.
>
> > TIA,
> > Dennis
>
>  
>

Reply via email to