"Make component" grayed out?
-
@harnstein said:
Sure i have some of Fredo's plugin installed
I don't know if all of them are up to date-LibFredo 3.7 has an Check for Update function.
-
@harnstein said:
PS: something off-topic, so i don't have to start a new one.. i remembered there was a tool "keeping tool active / persistant (recalling the tool to use i a couple of times) and i remember it was from you, thom. am i right? i couldn't find it by searching. today i thought it would come in handy .. thanks.
hmm... no, not something I recognize...
Maybe TIG?
Check the Plugin index (Big red Plugins button at the top of the page.) -
@harnstein said:
I prefer making components from groups, this saves me from naming components (they just take the name group#xy).
A little off topic but why do the extra work of making the component from a group? You don't have name a component when you make it. Just hit G (G is the default shortcut for Make Component) and Enter. The name will be Component#1, Component#2, etc.
-
A little off subject.
Well I have never been able to get Diggsey’s Recurve to work. It was always grayed out in the context menu. So last night I started the exercise to find out which plugin was causing the trouble.
I found out that if I didn’t load Fredo’s scale plugin, than Recurve would be ungrayed. I have checked and I do have all of Fredo’s plugin up to date.
Just thought I would pass this along. I have been looking into Fredo’s scale plugin to see if I could remove the context menu options. Way to complicated for my Ruby knowledge.
Ken
-
@dave r said:
A little off topic but why do the extra work of making the component from a group? You don't have name a component when you make it. Just hit G (G is the default shortcut for Make Component) and Enter. The name will be Component#1, Component#2, etc.
Ah, alright, sometimes i'm just stuck in old ways. Good idea. Thank you!
@thom: I'll dig throught that, i think it has to be somewhere between these icons in front of my face... There could be some record function as well (like photoshop actions) select some element and "play" the recorded set of actions...? Was just wondering.
_h
-
-
@unknownuser said:
I found out that if I didn’t load Fredo’s scale plugin, than Recurve would be ungrayed. I have checked and I do have all of Fredo’s plugin up to date.Ken
Ken,
What does matter is that you have LibFredo6 up to date. FredoScale uses LibFredo6 for generating the contextual menus.
Please tell me if this fixes your issue
Fredo
-
@unknownuser said:
@unknownuser said:
I found out that if I didn’t load Fredo’s scale plugin, than Recurve would be ungrayed. I have checked and I do have all of Fredo’s plugin up to date.Ken
Ken,
What does matter is that you have LibFredo6 up to date. FredoScale uses LibFredo6 for generating the contextual menus.
Please tell me if this fixes your issue
Fredo
Fredo
Yes I did have LibFredo6 while I had this problem.
Today I have been removing plugins right and left and now they both work while loaded at the same time. I believe it was just an overload of plugins.
I have also been modifying plugins not to use the context menu. With my limited Ruby knowledge this takes some time. Heck, I may be the cause of some of my problems.
Not sure why plugin authors use the context menu when it seems to be causing problems. Also, I wish, the plugin authors would make it apparent on how to remove the context menu option.
I believe this is like another time I had this problem, one plugin would appear to cause trouble, but in reality it was just an overloaded combination of plugins and not one particular plugin. Didn't mean to imply that your plugin was causing the trouble, just looking for help.
Right now, I believe I have a stable system.
Fredo, thank you for your reply. I have to stop loading up plugins that I don't use and stick with the few that I don use.
Again thank you.
Ken
-
@unknownuser said:
Not sure why plugin authors use the context menu when it seems to be causing problems. Also, I wish, the plugin authors would make it apparent on how to remove the context menu option.
Because so many plugins where made before this was known to be an issue.
-
@unknownuser said:
Also, I wish, the plugin authors would make it apparent on how to remove the context menu option.
In most of my plugin, go to the Default Parameters dialog box. You can select which menu should appear in the context-menu (check-boxes are toward the bottom of the dialog box).
Fredo
-
Thanks Ken for tracking down the issue with recurve being grayed out. I disabled FredoScale from appearing at all in the context menu and now it's working properly, along with a few other grayed out items. Now to track down what is causing my Selection Toys toolbar to go missing....
-
@unknownuser said:
@unknownuser said:
Also, I wish, the plugin authors would make it apparent on how to remove the context menu option.
In most of my plugin, go to the Default Parameters dialog box. You can select which menu should appear in the context-menu (check-boxes are toward the bottom of the dialog box).
Fredo
Sir
Darn now I feel stupid. I forgot about the options to make changes in the operation of your plugins.
Ken
-
I've noticed that tools are sometimes grayed out on my toolbars, but when I click them, they activate right away. So why are they grayed out in the first place? Most tools do not display grayed out. I'm not using any plugins, btw, just the free SketchUp.
Advertisement