Integrating a DRAWMENU into an INPUT form. HELP!

[Spybot]

Hello!

Guys, is there a way to integrate some buttons (generated by DRAWMENU command) into the INPUT form? I mean like a HELP button, then associate an action to it.

I already got the buttons with mouse properties, I just can't integrate them together with the INPUT command form. Is it possible or am I just dreaming?

Thank You!

[Han]

(11-15-2016 07:18 AM)Spybot Wrote:  Hello!

Guys, is there a way to integrate some buttons (generated by DRAWMENU command) into the INPUT form? I mean like a HELP button, then associate an action to it.

I already got the buttons with mouse propierties, I just can't integarte them together with the INPUT command form. Is it possible or am I just dreaming?

Thank You!

It is currently not possible using the built-in INPUT command.

[Spybot]

Thank you Han! I Guess the only choice here is to generate my own INPUT form using the graphical commands available.

[Tyann]

Bonjour

Si le but est d'afficher un commentaire d'aide pour les entrées
cela est prévu dans la commande INPUT.

Hello

If the purpose is to display a help comment for entries
This is provided in the INPUT control.

[StephenG1CMZ]

(11-16-2016 06:10 AM)Tyann Wrote:  Bonjour

Si le but est d'afficher un commentaire d'aide pour les entrées
cela est prévu dans la commande INPUT.

Hello

If the purpose is to display a help comment for entries
This is provided in the INPUT control.

The HELP referred to in the INPUT syntax consists of one line of text - and is always shown.
Whilst that can be sufficient, being able to tap Help and see a page-full of text (perhaps diagrams too), when you need it, would seem much more responsive to the user.

[DrD]

The INPUT() help parameter is useful as a hint for the input variable requirements. I think the current approach works well. If a program developer wants to provide even more detail, additional information could be given as a result of the user's response to the INPUT() variable itself:

// fragment (input subroutine, for example)
INPUT(X);
IF X==0 THEN You_Can_Provide("All kinds of additional info"); // Help hint: "0 for more info, +int for good, -int for evil," etc.
END;
// ... or some variant of this idea

[Spybot]

Hi Guys!

I'm aware of the help parameter included in the INPUT command. It is just not enough for the kind of help(Graphical help) I want to display. I need to add a softmenu button, which will be there all the time, even if I don't enter any data.
I'm planning to create my own INPUT form, then I can add as many buttons I want.

[DrD]

But at what cost? For the sake of discussion, if you have the "bound to's," you can do most anything. In terms of ppl efficiency, and practical implementation, to me it seems like adding a menu driven help parameter would just result in way more command bloat than return value, for the purposes of the ppl INPUT() construct.

An external input form could be a useful as an exercise in programming skill, but I sure would be surprised if the product has much utility value, afterwards. Do you have greater expectations for the input form than just this one-time objective? (I have made quite a few ppl programs, many using grob techniques, but I haven't encountered "lack of" a more robust help parameter as a bottleneck).

Given the mission purpose of the hp prime, ppl is about where it should be. If the product itself was designed for engineering/professional users, the entire programming language needs to be reviewed.

-Dale-