"set cursor to busy" not working in revweb?
janschenkel at yahoo.com
Sat Nov 14 09:47:04 CST 2009
At the risk of sounding like a broken record: have you filed this in the Quality Control Center? I had a quick search for the words revlet and cursor (both together and apart), and couldn't find such a report.
It only takes a minute to fill out a bug report, and the more information they have (example script or ven a complete example stack), the quicker they can find the underlying cause.
The good news is: since the release cycle of the revWeb plug-in is separate from the revMedia/Studio/Enterprise IDE, this sort of corrections can be release separately in an incremental patch.
But the best way to ensure the RunRev team tackles this, is to report each problem you encounter. And until they implement a fix, you can look for a workaround.
In this case, you could disable controls, maybe overlaying everything with a white rectangle that has blendlevel 30, and on top of that a regular progress bar, or even an indeterminate progress bar image.
Quartam Reports & PDF Library for Revolution
"As we grow older, we grow both wiser and more foolish at the same time." (La Rochefoucauld)
--- On Sat, 11/14/09, Richard Miller <wow at together.net> wrote:
> Unfortunately, despite repeated
> tries, I can't get an answer from Rev about this issue of
> setting the cursor to busy in revweb. I don't know why they
> would keep this info a secret and leave developers hanging
> on such a fundamental matter, but that seems to be the
> For now, I have to accept that this functionality won't be
> available any time soon in revweb. Is this what other
> developers are assuming as well? Obviously, I can build a
> field or button that alerts the user when the program is
> busy, but it's extra work I could do without.
> I'm not asking Rev to fix this now (though that would be
> nice). I realize they have a lot on their plates. But I am
> asking for information on this so folks like myself can take
> appropriate action.
> Richard Miller
> J. Landman Gay wrote:
> > Richard Miller wrote:
> >> Cursors were included in the build.
> >> Hard to believe a busy cursor can be considered
> > What I'm thinking is that the engine can't manipulate
> cursors at all (and I don't know how easy that is to do
> within a browser.) So I suspect by "custom" they mean
> anything that isn't the system cursor, which the browser
> applies by default.
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage
> your subscription preferences:
More information about the use-livecode