> On 30 Jan 2018, at 09:46, K K Subbu <kksubbu...@gmail.com> wrote: > > On Tuesday 30 January 2018 01:06 PM, Norbert Hartl wrote: >> Am 30.01.2018 um 08:26 schrieb "p...@highoctane.be >> <mailto:p...@highoctane.be>" <p...@highoctane.be >> <mailto:p...@highoctane.be>>: >>> On Tue, Jan 30, 2018 at 12:12 AM, Torsten Bergmann <asta...@gmx.de >>> <mailto:asta...@gmx.de>> wrote: >>> >>> >>> Cursor>>beCursor with Cursor being a Form makes a lot of sense on any >>> platform. >>> >> Sorry but Cursor>>beCursor does not make any sense on any platform :P > Could you be more explicit? > > If beDisplay makes sense for DisplayScreen why not beCursor for Cursor? While > a Cursor can be emulated in an image, it would be more efficient to use the > cursor support present in practically all graphics controllers these days.
I guess because a cursor and a display are already cursors and displays (hence the “be” does not has sense), when what you are trying to do is actually to “install” them or “use” them, or “activating” them :) Esteban > > TIA .. Subbu >
