Mouse pointer while a Retrieve

Carles Molina

unread,

Dec 14, 2000, 3:16:41 AM12/14/00

to

Hi, I'm using PB6.5 and Oracle 8i

I do a retrieve like follow:

SetPointer(HourGlass!)
DW.retrieve()
SetPointer(Arrow!)

and in the retrieverow event of the datawindow I've have the next script to
show how many rows there are.

st_1.text = String(row)

How can stay the mouse pointer to Hourglass! during the retrieve ?
If there is no script in the retrieverow it works. But when i write some
code in the retrieverow the mouse cursor always turns to arrow.

Thanks,

kat...@banet.net

unread,

Dec 14, 2000, 8:52:13 AM12/14/00

to

You can make another call to SetPointer in the RetrieveRow event.

Basically, a SetPointer call will have effect for the duration of the
current script. As soon as you begin executing a different script (even
one called from the first script), the pointer is reset to the arrow.

steve
[TeamSybase]

Carles Molina

unread,

Dec 14, 2000, 12:16:42 PM12/14/00

to

But then i have the efect:

HourGlass, Arrow,HourGlass, Arrow,HourGlass, Arrow,HourGlass,
Arrow,HourGlass, Arrow.....

The mouse pointer change very fast from hourglass to arrow and viceversa,
and that produce an ugly efect.

<kat...@banet.net> escribió en el mensaje
news:94B8B72B886C5792004C3107852569B5.0031D62E852569B5@webforums...

Jakub Janda

unread,

Dec 14, 2000, 1:38:35 PM12/14/00

to

Yes, PB resets the mouse pointer to Arrow! and you set it to HourGlass!. I
think there are two ways to soulve your problem, try them if they work.
a) You set the Pointer property for your window, dw and maybe all other
visual objects to HourGlass! before retrieve and set it to nothing (i.e.
default) after retrieve. You don't do any SetPointer(). This will work for
sure, but is clumsy.
b) You can try to play with SetRedraw() function. You set the window
SetRedraw() to false before retrieve and on retrieve row you change pointer
to HourGlass!, set redraw to true, write the "st_1.text = String(row)" and
set the window SetRedraw() to false again. After retrieve, you set redraw to
true again. Warning, I am not sure this will work.

Jakub Janda

Jerry Siegel

unread,

Dec 14, 2000, 2:54:15 PM12/14/00

to

Somebody posted a solution for the flickering pointer using the SetCapture
API - try searching for it with www.deja.com .

Jakub Janda wrote in message <1aVUM8f...@forums.sybase.com>...

Simon Caldwell

unread,

Dec 20, 2000, 5:22:11 AM12/20/00

to

IIRC, putting SetPointer(HourGlass!) in the RetrieveStart() event will fix
this. You may also need to put it in the RetrieveRow() event, I'm not
sure - try it and see.

S.

--
Simon Caldwell
Get Real Systems Ltd
Holtby Manor, Stamford Bridge Road, York, YO19 5LL
Tel 01904 481999 Fax 01904 481666
Visit us at www.getrealsystems.com

Specialists in e-Procurement and supply chain technology

"Carles Molina" <c...@hipra.com> wrote in message
news:rYPBJha...@forums.sybase.com...

Bug

unread,

Dec 20, 2000, 10:53:55 AM12/20/00

to

Just a side note, though I'm sure you already know this. But, putting
code... any code--even a comment... in the RetrieveRow() event really kills
performance. You could put a computed column in your datawindow footer that
shows the number of rows, but you'd have to leave Redraw on for the user to
see it updating. And having the redraw on is also a performance killer, but
at least it would leave your hourglass alone.

"Carles Molina" <c...@hipra.com> wrote in message
news:rYPBJha...@forums.sybase.com...

Carles Molina

unread,

Dec 21, 2000, 2:50:10 AM12/21/00

to

Yes, it really kills it. We have decided not to show the number of rows
while retriving.

So, my problem is fixed.

Thanks to all.

"Bug" <jfe...@mmm.com> escribió en el mensaje
news:d8c167p...@forums.sybase.com...