>>I developed a POS and Restaurant POS and I think this's
>>not a applicable way. A POS application should be so fast
>>(Wait for a while for finder) and so easy (cashiers are usually
>>people just graduaded high-school (difficultly) and their
>>mind confuse so easy).
>
>
>It doesn't have to be employed everywhere, and employing it everywhere doesn't make it slow. It would work for POS systems. And if it was put into a generic class, it could be turned off or on with settings at design time, or run-time.
>
>With touch-screen devices you lose the right-click. In certain places, having a long-press mimic the right-click would be desirable. This method I have outlined makes it possible. It doesn't have to be used anywhere.

Hrm... Perhaps we should not be thinking in terms of having two or three-button mouse?
How are varoius operations handled when you have a single-button mouse (as typically associated with Macintosh)?
How about popular touch devices such as iPad or iPhone? or Android tablets?
.. and let's not forget the obvious -- how do we use Web pages? Come to think of it, I don't recall using right-click much on Web pages...