Crazy problem with Right Click

solo · 28 Apr 2010, 15:20

Any news on a bug fix?

As this and the nomadic toolbar is making for a lousy SU experience.

Gaieus · 28 Apr 2010, 15:21

I have gotten rid of the toolbars (undocked them) long ago. This has no fix as of yet. What I guess they won't even fix it in this release although you never know what these SU Folks come up with any time.

TIG · 28 Apr 2010, 15:24

Couldn't agree more...
The last response from Google was that they 'were looking into it' ... 'but the next version is taking most of their resources, as it's more important'... but, as I said, 'It'd be a good idea to fix some of these basics first' - to avoid the risk of alienating a lot of users immediately who might not then look at v8 after their v7 woes...

jpalm32 · 28 Apr 2010, 16:05

64 Bit support is well over due!
I'm getting really frustrated with SU. Don't get me wrong, it's useful but there comes a point...
Makes one appreciate the qualtity of work that goes into AutoCad. Used it on a W98 doing a large complex, can't remember it crashing. Not that Autodesk has any better attitude.
I really appreciate the talent of you guys that have mastered it and the renderings. I send your work to many people.

jpalm32 · 28 Apr 2010, 16:15

As a side note: My wife does large legal docs in Word and says she has a problem when she uses right click often, needs to save and reload doc.

thomthom · 28 Apr 2010, 16:59

At work I've been forced to diable most of my plugins - as that improve the situation. But the folder fill up as I need to re-add plugins as I need them.

lapx · 28 Apr 2010, 17:31

This and the nomadic toolbar is amateur and should be fixed immediately
While im on my horse there needs to be better transition form cad circles to sketchup!
What are these guy's at google doing all this time, playing ping pong!

solo · 28 Apr 2010, 18:48

@unknownuser said:

What are these guy's at google doing all this time, playing ping pong!

Planning base camp 2011 Hawaii maybe?

jhauswirth · 4 May 2010, 22:42

The problem is Ruby scripts are calling-
UI::Command.new
and not attaching the new command to a menu item.

If you want to verify this run-

for i in 0..1000 do
cmd = UI::Command.new("Tester") { UI.messagebox("Hello World") }
end

I can see Ruby scripts creating new commands on each right mouse click.
Every new command creates a unique command ID in SU and there are only 1000
command IDs available. Normally a command is attached to a menu and when
the menu goes away the IDs are recycled, but since these commands are not
attached to a menu, they don't get recycled.
I'm going to try and figure out how to dump the list of commands (they have
menu item text) so that people can see who's causing the problem.

thomthom · 4 May 2010, 22:55

Ah! This is great news!

The Mighty Bug Hunt of 2010 is now officially open!

thomthom · 4 May 2010, 23:08

@jhauswirth said:

I'm going to try and figure out how to dump the list of commands (they have
menu item text) so that people can see who's causing the problem.

ObjectSpace.each_object(UI::Command) {|x| p x }
Gives you access to each UI::Command object. But the class has only setter methods defined. And instance_variables on an instance of UI::Command returns empty.

thomthom · 4 May 2010, 23:18

@jhauswirth said:

Normally a command is attached to a menu and when
the menu goes away the IDs are recycled, but since these commands are not
attached to a menu, they don't get recycled.

What is the command is used in both menus and toolbars? or just toolbars?
I often create an instance of a Command when both a menu and a toolbar is executing the same command.

jpalm32 · 4 May 2010, 23:23

[quote="thomthom":287u3y55]
@jhauswirth said:

I'm going to try and figure out how to dump the list of commands (they have
menu item text) so that people can see who's causing the problem.

ObjectSpace.each_object(UI::Command) {|x| p x }
Gives you access to each UI::Command object. But the class has only setter methods defined. And instance_variables on an instance of UI::Command

Yeh! What ThomThom said.
Really! You guys scare me sometimes.

jeff hammond · 4 May 2010, 23:42

interesting turn of events..
i've read a lot of these right-click posts and thought they were something to do with windows because i've never experienced the problem or heard of another mac user with the problem.
sounds like it should affect mac users as well then.. maybe none of the mac users here have the trouble ruby installed?
must be one of those windows specific exporters or something?

[edit] hmm.. well, except for the fact that it's been reproducible without using plugins at all

thomthom · 4 May 2010, 23:52

@unknownuser said:

[edit] hmm.. well, except for the fact that it's been reproducible without using plugins at all

By right clicking repeatedly on geometry without cancelling the menu. But the menus then usually returns ones you cancel it.

jeff hammond · 4 May 2010, 23:56

@thomthom said:

@unknownuser said:

[edit] hmm.. well, except for the fact that it's been reproducible without using plugins at all

By right clicking repeatedly on geometry without cancelling the menu. But the menus then usually returns ones you cancel it.

i shit you not, i just tried rightclicking on a square at least 800 times .. no glitches

thomthom · 5 May 2010, 00:07

@unknownuser said:

i shit you not, i just tried rightclicking on a square at least 800 times .. no glitches

Did you right click
and then while the menu was still open right click again?
(on the same entity)

thomthom · 5 May 2010, 00:14

Here's a little hack I made. It intercepts all the setter methods and prints the arguments to the console. Named "_0.rb" to make it load first. (or does underscore make it load last...?)

For some reason it is not overriding the initialize method.

But I do intercept the setter methods. On my home machine I get some output every time I right click:
tooltip: Scaling with orientation of scaling box tooltip: Tapering with orientation of scaling box tooltip: Planar Shearing with orientation of scaling box tooltip: Planar Shearing by selection of plane and angle tooltip: Stretching with orientation of scaling box tooltip: Twisting with orientation of scaling box tooltip: Rotation with orientation of scaling box tooltip: Rotation by selection of plane and angle tooltip: Radial Bending by selection of plane and angle tooltip: Make Groups and Components Unique

And when I do this line for every right click:
c=[]; ObjectSpace.each_object(UI::Command) {|x| c << x }
the count goes up by 10 - one for each tooptip.

So in my case, even though I'm not catching the new method, it does appear that I've accounted for every leak. There might be other plugins that does not set any other methods when it creates a new Command object, so I'm not sure how to catch that since I can't hook into initialize.

As for the tooltips, they are from FredoScale, right?

_0.rb

jeff hammond · 5 May 2010, 00:14

yes..

drew a rectangle then started right-clicking repeatedly on its face.. (didn't do anything else other than those two steps.. no left-clicking,selecting, or moving the mouse pointer etc.)

thomthom · 5 May 2010, 00:14

@unknownuser said:

yes..

drew a rectangle then started right-clicking repeatedly on its face.. (didn't do anything else other than those two steps.. no left-clicking,selecting, or moving the mouse pointer)

You must be charmed.

Crazy problem with Right Click

If you want to verify this run-

for i in 0..1000 do cmd = UI::Command.new("Tester") { UI.messagebox("Hello World") } end

for i in 0..1000 do
cmd = UI::Command.new("Tester") { UI.messagebox("Hello World") }
end