[Plugin]ContextMenuOptimizer v2.8 (menu gray-out issue fix)
-
Thom, i'm quite sure the selection toys are causing the issue on my pc - so the google fix is not working after all
when i remove S.T. the menu does not grey out even after hours of working
-
That is very odd. I can not reproduce it. Nor does it have the code that Google said caused this.
How many plugins had you got installed? I wonder if one might run into this if one just has many menu items - Selection Toys has quite a few. Have you tried disabling some of the menu items?
-
thanks that's a good idea, might just be it...well hope so.. after all together there must be something like 500 or 600 plugins in there by now..
-
@cadfather said:
thanks that's a good idea, might just be it...well hope so.. after all together there must be something like 500 or 600 plugins in there by now..
Well - that might very likely be the cause. Google said their limit of Command objects where at about 1000 - if you ahve that many you might hit some limit even without some leak like Fredo's tools.What would be interesting is if you could install one more. (No worries no menus or anything )
Then open your Ruby Console and type instats
- see what it reports.
Then do some right clicks and see what it reports afterwards.
-
well, 600 was my very quick estimate of all the commands in the folder from didier's spray comps to su2kt
but the stats gives this: (cool thing) - UI:Command objects: 283 of 1000 (28.30%)
so i guess that's still not too greedy..
-
Does it increase during usage? After right-clicking for instance?
-
not for the moment - i think it needs more work-time - i'll put it through the paces this afternoon though.
to be continued..
-
Then it can't be the same issue, because you should see increase immediately. (However, you might get different results from what you right click on, Edge,Face,Group,Component.)
-
i see.. i shall let you know how i get on, i have some work later so i will be able to test it properly..
meantime i disabled the selection toys i don't use so much, so i'm preparing for sunshine through the clouds! -
CadFather
Do you use my plugin?
I think it should solve such issues. -
hi Alex
yes i did as soon as i saw it.. but the result was that only some menus 'refreshed' - some other (strangely the sketchup ones like activate section plane, reverse face etc) were still grey
-
@cadfather said:
hi Alex
yes i did as soon as i saw it.. but the result was that only some menus 'refreshed' - some other (strangely the sketchup ones like activate section plane, reverse face etc) were still grey
My plugin does not allow a possible memory leak, it protects the buffer menu.
And I wrote about it:@alexmozg said:
...unfortunately, the predefined context menu commands
(such as Explode, Hide, Erace etc.)
are not amenable to correction,
but the commands of other plugins should always work.My colleagues and I use my plugin and we are not experienced this issue any more. But we have limit plugins in use, basically most necessary.
-
OMG all my menus are greyed out from the start with or without this plugin!!! What is going on?
-
You may have too many context-menu / commands running - do you have many plugins ?
Temporarily remove any you recently added and see what happens... -
@chango70 said:
OMG all my menus are greyed out from the start with or without this plugin!!! What is going on?
Have you updated any Fredo plugins?
-
Fredo's latest CurviLoft... has/needs 'Lib3.5' BUT I've found that 'Lib3.4c' [the one that was issued to stop this very problem] is still needed by Fredo's other tools to stop the dreaded graying out issue - if you don't use this 'optimizer tool'...
-
thx for the quick reply guys.
Yes I do have lots of plugins.
I will try removing them.
-
@tig said:
Fredo's latest CurviLoft... has/needs 'Lib3.5' BUT I've found that 'Lib3.4c' [the one that was issued to stop this very problem] is still needed by Fredo's other tools to stop the dreaded graying out issue - if you don't use this 'optimizer tool'...
Argh... Curviloft is so much fun.. I guess ill try uninstall that.
-
Try to update all your Fredo plugins and have the latest 3.4 and 3.5 of Fredo Lib.
-
It appears as though fredoscale and fredo's ghosted components where the culprits. I removed them and the menu came back...
Advertisement