You are now editing multiple components

ashscott

Doesn't need to add another keystroke, it could just modify the watermark in the top left hand corner of the screen. Normally there would be no watermark but when you are modifying a manifold component the number of components currently being modified would be displayed.

No extra keystrokes required.

Have seen this watermark modification done within sketchyphysics before...

Krisidious

Oh so just information... not a dialog box that you have to hit ok on... I'm down.

ashscott

Well, once you've got it reading and returning the info you want I can't imagine its much work to change how the info is presented to you whether a watermark or dialogue box

jeff hammond

@krisidious said:

If that were the case there should definitely be a way to turn it off.

there's already a way to turn it off.. close the entity info panel

Krisidious

Nice try Jeff but that only works while you have it selected, not while editing.

jeff hammond

is there a difference?
(practically speaking)

Krisidious

Yeah, I don't select components... I just double click them.

ashscott

And coz Im clutter-phobic I only turn "Entity Info" on when I need it

jeff hammond

@ashscott said:

And coz Im clutter-phobic I only turn "Entity Info" on when I need it

right.. like when you want to check if a group is solid or how many copies of them you have in a model..

jeff hammond

[edit] oh.. and hey.. i'm not knocking your idea in a way it may appear..

just seems like the tradeoff between having this information being presented in a slightly different way than the native method..
-compared with-
needing yet another plugin to load and (as i understand) running at all times..

isn't worth it

Krisidious

I do have way too many already.

Chris Fullmer

This is a plugin that in theory could run fairly silently in the background. Wouldn't even need a menu item.

Double click on a component and a little window pops up and tells you that their are X other identical components. Or even just a note that reminds the user that this is a component. It could be fairly useful I think. If it was not too intrusive.

ashscott

It would have no interaction from the user and would only be a few lines of code can't imagine it would slow anything down.

jeff hammond

@ashscott said:

It would have no interaction from the user

right.. that's where i was concerned.. the user can't switch it on or off.. it's always on.. even though you'll only use it for maybe 1/10000th of your session time..

@unknownuser said:

and would only be a few lines of code can't imagine it would slow anything down.

possibly.. i simply don't know and as of late, i'm just weary of having too much going at once due to stability issues..

but chris who posted above you likes the idea ANd knows ruby.. and if he says it's ok then it probably is..

but you sort of messed up in your 'request' for a plugin because you said:

@unknownuser said:

I wanted to write this as my first ruby project but it seems slightly trickier than a total ruby noob like me can handle.

so now you've put the ball in your court

get a few lines going and post in the developers forum when you hit a brick wall.. then ask them for a little steering in the proper direction

[or, of course.. get lucky and open this thread in the morning and find that someone wrote it while you were sleeping ]

[edit] oh wait.. you're in NZ.. so the sleeping & morning thing might not work out in exactly the same way i've described there..

ashscott

The point of the plugin would be to stop accidentally modifying components.

If you had to turn it on and off it would defeat the purpose because you would accidentally start modifying a manifold component and unknowingly modify all copies of that component.

It would not be intrusive because it could just induce a watermark popup in the corner of your screen.

Chris seems to understand what I'm getting at.

I have no idea what I'm doing but perhaps something like this is a start:

def onOpen(instance) setVar ("X","definitions.count") end if componentinstance.manifold? = true setVar("text","You are currently editing {getVar("X")} components") end if componentinstance.manifold? = true getVar ("text") end

Don't laugh, I've just started reading the ruby documentation this week.

To put it in terms that I actually understand:
If the user opens a component to edit it
Count how many instances of that component are manifold with the one the user has open
Call the number counted "X"
Display "X" within this sentence as a watermark in the top left corner of the screen:
You are currently editing "X" components

Also, I'm from NZ but living in India

Chris Fullmer

What does the manifold bit have to do with it? Why do you only care if it is manifold? It would be more applicable to more people I would imagine if it worked on all components, not just the manifold ones I would guess.

Also, I could be wrong, but the notion of this popping up and disappearing on its own is actually a bit more complicated then might be first suspected. It will require an observer to be running at all times, so it will add a little overhead to the system. Anyhow, I would be interested in trying to make it work, see if its simple and stable.

Krisidious

I thought he was talking about the actual manifold plugin... what do you guys mean manifold?

ashscott

I've probably misunderstood what manifold means. I thought it meant that a component had other components that would be modified along with it?

Perhaps there is a more computationally straightforward way of notifying the user?
A simple UI popup seems to cost very little but, as someone pointed out, that requires the user to click "OK" each time they open a component.....

jeff hammond

@krisidious said:

what do you guys mean manifold?

i take that to mean that the object is solid or watertight..

as in: if entity info reports "Solid Component (9 in model)"
it could instead say "Manifold Component (9 in model)"
and mean the same exact thing.

Dan Rathbun

@chris fullmer said:

Also, I could be wrong, but the notion of this popping up and disappearing on its own is actually a bit more complicated then might be first suspected. It will require an observer to be running at all times, so it will add a little overhead to the system. Anyhow, I would be interested in trying to make it work, see if its simple and stable.

I whacked out an example yesterday.
Serves a good example of how to dynamically have SketchUp attach observers to models as they are opened.

It uses a "view based" model note,... tagged with an empty attribute dictionary, named with the plugin's OPT_KEY. (The transparency of the note is controlled by the user, via the Model Options dialog, in "Fade Rest of Model".)

[Code] (EXAMPLE) Edit Mode Warning Flag