Posts made by flyashy

erm..
could be that the vcb considers the 's' in 5s as segments and thus does not consider the following keypresses? i don't know about the 'e' though..

thanks escapeartist,
i must try that out next time i get the jinx

Okay end of experiment.
in short,

Heavy file + Lots of plugins + repeated right click = grayed out menu.

back to a less engorged plugins directory...

sigh

@TT,
erm..I didn't try the exploding instance method before moving the plugins, but yes I could right click and get the greyed out menu.
right now in the process of picking out the non submenu scripts and putting them back to see if the greying out happens or not..
lessee..

Hi Tig,
nope. didn't happen when I made copies of components and exploded one instance. In fact I went around like a madman right-clicking everything in sight too just to make sure.
The only difference being I'd emptied my plugins directory. Just moved everything including the examples folder to a temp folder.

I also opened up some of the fairy complex models to check if it was the complexity of the file that prompted this..nothing. No greying out.

Could it be about scripts that have submenus in the context menu? I did not have any scripts that had submenus before this started happening.

thanks,
flyashy

Oh you posted this while I was typing..

So I guess I'll just go easy on the right click for a while then..the funny thing is that when the context disables even the shortcut keys don't respond..so it's probably the handlers as you mentioned..

thanks,
flyashy

Oh, so is this a bug with the upgrade?

@alpro said:

Don't think its a menu issue, I just finally upgraded last week and decided to keep my menus and toolbars as clean as possible and have only five plugins that I use most often insta....
Mike

Hi I started getting this since a few days too. I recently installed quite a few scripts and obviously it's one of them doing this. I thought it was lines2cyl.rb doing it because the grayed out right click seemed to happen soon after using it from the tools menu. so I removed the ruby from the plugins folder. but lo & behold, very weird, the 'convert lines/arc/etc to cylinders' command in toolsmenu is still there and refuses to go away. it's a little strange because it's supposed to be in the plugins menu isn't it?
Now I can't even get rid of it to check if that is the one doing it.

Sometimes the menu reactivates if I use 'Remove unsused edges' from the edit menu. ( I don't know what script does this one). sometimes not.

So, alpro, if you just have five plugins could you list them? That way we can probably figure out the ones which are common and see if any of this makes sense.

ta,
flyashy

Ah, thank you Chris & Rick,
after reading your replies I did open up some rubies and tried to figure out what you said, and will give it a go, although I'm more likely to break things than mend them
But then, i always liked to take things apart to see what made them tick.
Lesse
ta.

Thanks Gaieus

Yikes , I had forgotten all about this! Ti's been a year or so since I was @ sketchUcation. Wow.

@thomthom said:

Thanks guys. I plan to restart the series myself.

angusog; do you have the notes in digital form?

Okay, I have a lot of his books in digital format, so I'll try to locate the description and post it here.
and figure out what part i can model..

cheers,
flyashy

P.S. even after exploding and redefining the component the FOV distortion remains.

Actually I have figured out some more specifics of the problem. If I create the component straight off from a selection then the preview is as per the view but if I covert a group into a component, which incidentally, I end up doing a lot, especially with part of connected geometry, then the thumbnail FOV is distorted, so much so that the component is pretty much unrecognizable.

Is there any way to redefine the TN preview except exploding and remaking the component?

thanks,
flyashy

Hi,
I was wondering if there is any way to ensure that the thumbnail of the preview is a reasonable 3D view while making a component? There are times when I get extreme views of the components which are pretty much unrecognizable in the component browser. do I have to re-orient the view to certain angles or change the FOV or something?

thanks,
flyashy

Remember that once you've changed the arc/circle segment resolution ( by typing the number of segments in the mesurements window while drawing them i.e. 100s instead of 24s etc) it remains that way until you change it again.

For example let's say you're drawing a 50' Dia. Circle it'll be all right to type in a large number of segments, but then it'll stay at that number for any new circles you draw. so you might end up drawing 200 segment circles for a 3" dia Pipe component and your model will just collapse under all the weight of edges!

The easier way to have finer segmented curves is to change the resolution afterwards from the entity info window.

Uh..Sorry to inform you that Major Critiques is right now vacationing in Bahamas. I suggest you talk to Capt. Feed Bach instead.
Regards.

lol..just a little joke...sorry couldn't resist that!

Hi all,
I recently discovered all those brilliant scripts you all kind peoples have made available here. So I'd like to thank you all for them.
Okay, so I went a little overboard with them and installed virtually every script I hoped to use, and thus began my predicament, a virtually non-memorizable(is that even a word?) context menu. Since I'm a more of keyboard shortcut and right click kind of guy I don't particularly mind the plugins menu getting messed up too much but I'm a little possessive of my right click menu.
Now i searched the forum and found out about the Organizer.rb by Rick W, but that script does not organize the context menu or am I wrong in that assumption?

Also has anyone else written any other scripts around this issue? I don't know any ruby, tho am eager to try simpler(novice level) tweaking if I could get some help/guidance/pointers/tips.

Thanks,
flyashy

I wonder if we can make the model selectable in terms of detail.
I'm not sure how to put this across, but what I mean is within the model or the map, there may be click-able sectors,within which more click-able bits, so that the entire model is not loaded at once and as you 'zoom' in or out the level of detail changes.
Sort of like a game or even Google earth.
It'd be a case of making different models with changing components I suppose. That way whoever wants can get really detailed with a little part of the model, but the overall viewing of the model does not suffer.

A beautiful, extremely useful and aptly titled script, Whaat.
Thank You.
Since you mentioned that you're not going to be working on this anymore, just wanted to inquire if anyone was doing anything with it to resolve the parallel projection usability. That would increase the usability of this tenfold or more.
I wouldn't mind doing it but I don't know anything about rb, except to use them
Ta,
Ashy

Again, Thank You!
Ashy