Hi Lazarus gurus,

I have an application which is bound to be used with a touch screen and without a mouse.
I'd need to show a hint when some components are touched (=clicked).

Is there an easy way to cause the component hint to be displayed, or the only way is to reimplement all the functionality of a show hint on an on OnClick event?

Any ideas?

Giuliano

Hi Lazarus gurus,

I have an application which is bound to be used with a touch screen and without a mouse.
I'd need to show a hint when some components are touched (=clicked).

Is there an easy way to cause the component hint to be displayed, or the only way is to reimplement all the functionality of a show hint on an on OnClick event?

Any ideas?

Giuliano

I don't have a no mouse system to test.
What happens when you do

procedure TForm1.Button1Click(Sender: TObject);
begin
  CursorPos:=TWinControl(Sender).ClientToScreen(Point(1,1));
  Application.ActivateHint(CursorPos, True);
end;

?

Mattias

Il 15/03/2015 18:48, Mattias Gaertner ha scritto:

I don't have a no mouse system either in this moment, but it looks quite promising.

Without the OnClick event you suggested, the hint did disappear or not show it I was too quick when I was clicking the control. With it the hint either stays there or shows. Tomorrow at work I'll test on the real system, but I'm confident.

Thanks a lot Mattias!

Giuliano

Giuliano Colla wrote

I'd need to show a hint when some components are touched (=clicked).

Why not incorporate a web design in your user interface. Many websites have a small "information" icon next to components. Click those and a hint window is show. Do the same with your app, and I would even implement a custom hint window to make it more attractive as it is a kiosk type app.

Regards,
- Graeme -

Il 15/03/2015 20:43, Graeme Geldenhuys ha scritto:

Thanks for the tip, but what I need is just a lightweight troubleshooting help, such as provided by a hint.
I'm dealing with the human interface of a family of automatic machines to make checkbooks.
When some problem happens, a synoptic of the machine is shown, displaying the current state of all the sensors of the section involved, with the one(s) causing the error highlighted.
Most of it is self-explanatory, and the operator doesn't usually need anything more, but to ease troubleshooting a supplementary information may be helpful, such as where the sensor is physically connected (e.g. "Box #2, Input 15"), or , depending on the display style selected, the more precise description of the sensor location and purpose("Blade motor encoder", "Binder temperature", "Feeder 2", etc.).

Giuliano