[Fixed]1.8.0 GUI.forceOSCursor

[tatt61880]

Edit: (by tatt61880 on 2011.10.23 13:15)
Fixed in 1.9.8 beta! Thanks

* NEW: Added selected tool icon to cursor - congratulations, tatt

-Tatt
----
"GUI.forceOSCursor = true;"
and
"GUI.forceOSCursor = false;"
seem to return the same result.

This Thyme command is something to do with "Show the tool size with cursor." and "Differences in cursor for each tools"

[emilk]

Algodoo used to have custom cursors for some tools, but that produces a problem: at low frame-rates the cursor lagged. Which was very irritating. (Try using brush tool with a low frame-rate and you see what I'm talking about). So I reverted this behavior to again always use the frame-independant OS cursor.

Of course, you can set custom cursors by talking directly to the OS directly, but this is a bit of a hassle since Windows and Mac will have different methods for doing this - and on Linux you can just forget about it.

But I agree, it would be nice with individual cursors (again). Maybe one day.

[tatt61880]

Cannot this trade-off be users' choice?
I feel forced OS cursor is more annoying. In actual, I use custom cursor with Phun and I don't feel the lag.

It's OK even if default cursor is current one.

[tatt61880]

Algodoo used to have custom cursors for some tools, but that produces a problem: at low frame-rates the cursor lagged. Which was very irritating.

GUI.cursorFPSLimit exists to solve this problem, doesn't it?

GUI.cursorFPSLimit - If the FPS drops below this, the default OS cursor will be used

[emilk]

I'll look at adding custom cursors for each tool in the near future.

[tatt61880]

I'll look at adding custom cursors for each tool in the near future.

Thank you.

[tatt61880]

Algodoo used to have custom cursors for some tools, but that produces a problem: at low frame-rates the cursor lagged. Which was very irritating. (Try using brush tool with a low frame-rate and you see what I'm talking about). So I reverted this behavior to again always use the frame-independant OS cursor. ...(snip)...

Is it possible to use custom cursor only when Sim.running == false?
This will solve lag issue, because we seldom make scene which lags without simulation.

[mori-d]

I'm missing lovely custom cursor...

Algodoo uses OS cursor anytime even if GUI.forceOScursor was false. (in 1.8.0 and 1.8.5)
Please fix this issue.

Algodoo is useless for my making scenes unless custom cursor came back.
Because I use short-cut keys heavily in making scenes and don't look at tools window.

I love custom cursor.

[tatt61880]

Algodoo used to have custom cursors for some tools, but that produces a problem: at low frame-rates the cursor lagged. Which was very irritating.

I noticed that the key point is "at low frame-rates".

I suggest to use custom cursor only when Sim.running is false (i.e. simulation paused), for the time being.
It's not perfect solution, but better than current forced OScursor.
How about this idea?

[electronicboy]

maybe if fps drops under a set limit, os cursor should be used.

[tatt61880]

Not yet fixed with v1.9.5b.

Algodoo used to have custom cursors for some tools, but that produces a problem: at low frame-rates the cursor lagged. Which was very irritating.

I noticed that the key point is "at low frame-rates".

I suggest to use custom cursor only when Sim.running is false (i.e. simulation paused), for the time being.
It's not perfect solution, but better than current forced OScursor.
How about this idea?

[electronicboy]

Not yet fixed with v1.9.5b.

Algodoo used to have custom cursors for some tools, but that produces a problem: at low frame-rates the cursor lagged. Which was very irritating.

I noticed that the key point is "at low frame-rates".

I suggest to use custom cursor only when Sim.running is false (i.e. simulation paused), for the time being.
It's not perfect solution, but better than current forced OScursor.
How about this idea?

problem with this suggestion is that it makes algodoo look inconsistant, and "sloppy...."

[TC42]

at low frame-rates the cursor lagged.

Don't most things lag at low frame rates...?

But I agree that it should be the user's decision; just because it is his decision doesn't mean that there has to be a visible button, however, a variable typed into the console would suffice.

[tatt61880]

But I agree that it should be the user's decision; just because it is his decision doesn't mean that there has to be a visible button, however, a variable typed into the console would suffice.

Same opinion.