Rotate Current View 2D (As though Z were out of the screen)

halroach

you should contact the smustard dudes, I'm sure they'll try to get it to work on OSX

Gruff

@unknownuser said:

I think this is what you are looking for.

Thanks Hal,

Works for me. This is the Cadillac tool.

Still think I'll roll my own pure rotator without a web form.

halroach

@gruff said:

@unknownuser said:

I think this is what you are looking for.

Thanks Hal,

Works for me. This is the Cadillac tool.

Still think I'll roll my own pure rotator without a web form.

Go for it!
It would be nice to have a visual screen rotation tool. with a similar diagram like with the 'rotate' tool, if you know what I mean.

RickW

It's a known issue, so I'm sorry I didn't get the notice put up on the site soon enough for many of you that this is currently a PC-only tool. Trying to get this to work on OSX has been a headache, and I've not had the time lately to fix it.

I'll post when it's ready.

jeff hammond

Thanks for replying Rick.
Apparantly, this script does things that I've always wished for in SU but I've been maced again

RickW

Short reply: I've made progress. I think I have it working now. Will post updated version to Smustard soon.

Long, geeky reply for other developers: I found out the problem is that Safari complies with the W3C spec for mouse events, and the spec itself is to blame. For some unknown, ridiculous reason, the W3C spec states a left mouse button should return 0, a middle mouse button 1, and a right mouse button 2.

In a brilliant move, MS decided that was dumb (how can you register a left click when it returns a zero? how can you register concurrent button clicks?), rebelled, and bit-coded mouse button events in IE as left=1, right=2, middle=4. Thus, 0=no mouse button events, 3=left & right mouse buttons down, 5=left & middle buttons down, and 7=all buttons down.

Unfortunately, I didn't realize that Safari and IE were returning different values for left click events, and that's why it didn't work on Mac.

The problem became checking for the mousedown event (which I had to solve by creating separate onmousedown checks for each slider; previously, xy positioning was sufficient) and mouseup events (removing the cursor pointer from the slider still allowed the slider to move, but failed to register onmouseup events, since the mouse was no longer on the slider - solved by creating a window outside of which the sliding stops). It's been a mess, but it works now.

Chris Fullmer

Wow Rick, thats good to know.

Can't we just switch to Chrome on both platforms and call it settled?

Chris

jeff hammond

@rickw said:

Short reply: I've made progress. I think I have it working now. Will post updated version to Smustard soon.

excellent!
can you post again in this thread when the update goes up? that's probably the easiest way for me to keep track.
thanks so much

Gaieus

Since the essence of the discussion has gone towards ruby, I have moved it to the plugins (or where the heck we are) dept.

RickW

@unknownuser said:

can you post again in this thread when the update goes up? that's probably the easiest way for me to keep track.
thanks so much

Will do.