[Plugin Library] LibFredo6 - v14.6a - 18 Sep 24
-
I have done every steps in the tutorial pdf file but It still doesn't work. I'm using Google sketchup pro 7.0.
-
I've tried what you proposed two times (once using safari and the other time using firefox)
and i only have these two file/folder :LibFredo6.rb
LIBFREDO6_Dir_34 folderi don't see these two anywhere :
ZLoader__FredoScale.rb
FREDOSCALE_Dir_20 folderThx for the answer!! maybe i'm just too dumb to make it work...
I will try again...
Thx for ur work i'm sure it's great... -
Sorry emperorgus, but have you read the first post of this thread and the PDF manual
This plugin do nothing by itself, it works in association with Fredo's plugins like Fredoscale, Round corner etc. So your two file/folder download of LibFredo is correct, BUT you need to download also the plugin you're interested in.
As Fredo wrote in this thread:
@unknownuser said:LibFredo6 is shared between several of my plugins. It provides a lot of basic functions (for instance the button palette management, the translation, and a large part of the interactive tools).
But for the user, it does not do anything by itself, unless used by the real plugins. -
@unknownuser said:
@agamemnus said:
Ok, I don't know exactly what's wrong but I am guessing it has to do with memory (undo/redo interference?) and/or interference with other functions. As I posted before, when I have this library active (the loader is in plugins), my flip, rotate, and group tools gradually become greyed out. The "greying-out" happens a lot faster on bigger models.
This can happen when I don't use any library functions, either.
I think the greying out of menus may happen anyway. I have seen a bug report about this issue in SU7 and 7.1
To all users : is this something you experience as well, and is it in relation with LibFredo6?Fredo
Greetings Fredo,
I can't wait to try these great new tools (TOS, etc.) ... the buttons and menu items are there ... but they are all GREYED-OUT (caps for emphasis only ... not yelling!) ... I've reviewed the pdf's and the posts for clues ... all the required folders are there in the right place (under Sketchup plugins folder) ... I've shut-down and restarted Sketchup multiple times ... to no avail. Will try stripping the plugins folder of everything except your stuff and see what happens. Please advise when you have a moment.
Thanks very much,
Louis Radakir
Ottawa, ON, Canada -
@louisr57 said:
... the buttons and menu items are there ... but they are all GREYED-OUT (caps for emphasis only ... not yelling!) ... I've reviewed the pdf's and the posts for clues ... all the required folders are there in the right place (under Sketchup plugins folder) ... I've shut-down and restarted Sketchup multiple times ... to no avail. Will try stripping the plugins folder of everything except your stuff and see what happens. Please advise when you have a moment.
Are you referring to the main toolbar and the main menus? If so this would be very strange, because there is no mechanism to gray them out in my plugins.
If you have a picture, it would help understand.Thanks
Fred
-
@unknownuser said:
@louisr57 said:
... the buttons and menu items are there ... but they are all GREYED-OUT (caps for emphasis only ... not yelling!) ... I've reviewed the pdf's and the posts for clues ... all the required folders are there in the right place (under Sketchup plugins folder) ... I've shut-down and restarted Sketchup multiple times ... to no avail. Will try stripping the plugins folder of everything except your stuff and see what happens. Please advise when you have a moment.
Are you referring to the main toolbar and the main menus? If so this would be very strange, because there is no mechanism to gray them out in my plugins.
If you have a picture, it would help understand.
Thanks
FredThe issue of loosing some right-click context-menu items [i.e. they get "greyed-out"] is a known bug with more recent versions of SketchUp - Google are being pressed to fix it...
Its cause is not wholly established, although having lots of plugins that make context-menu items and repeated clicking on objects seem to both trigger it - separately or together !
All of a context-menu's items still appear correctly under the last item in the main Edit Menu - so you can access them this way if the worst happens...
The only 'fix' is to save and restart SUp - then you should get back the context-menu, albeit momentarily.
Don't load plugins you aren't ever going to use - they increase the load and might just be the 'last-straw...' - move them out of the Plugins folder or rename them from.rbto.txt- that way you can always load them during a session by typing in the Ruby Consoleload"the_script_name.txt"...
-
thank
-
Thank you! Looks so useful - I can't wait to play with it!
-
[CRITICAL Upgrade - 6 May 10 - 23:55 CET - Bug fixing for the menu gray-out issue]
see http://forums.sketchucation.com/viewtopic.php?f=15&t=28135#p244052
Thanks to the clarifications brought up by jhauswirth, TIG and Thomthom about this ennoying problem, it is confirmed that LibFredo6 contributes to accelerate the apparition of the problem. Also included is a revised Spanish translation by Defisto.
So it is strongly advised that you upgrade to version 3.4c WHETHER YOU USE MY SCRIPTS OR NOT or disable my scripts in the menu Preferences > Extensions.For those who wants to have some details, the issue is that LibFredo6 may create Command objects everytime you use a contextual menu and never release them, whereas the maximum limit for SU is 1,000 commands. So everytime you right-click in the SU selection tool, you get closer to the limit where menus will start graying.
-
Thanks Fredo for fixing this so quickly. It's hard to even use sketchup without your tools.
-
Yes, thanks indeed
-
Fredo, your latest script lib v 3.4c completely greys out my right -click options as early as sketchup start up on 7.1 win XP. help?
-
@prismcnd said:
Fredo, your latest script lib v 3.4c completely greys out my right -click options as early as sketchup start up on 7.1 win XP. help?
Have you put it [and its related files] in the Plugins folder inside its own folder ?
-
Confirmed all files are in the proper placement. works fine without the "libfredo.rb" file, but with it as soon as i load sketchup and first action is right-click on sang all right click options are greyed out
-
Have you also updated FredoScale etc ?
-
@tig said:
Have you also updated FredoScale etc ?
No need. The code was in LibFredo. FredoScale did not have to be updated.
Tools on Surface did though.There could be some other culprit to the disabled menus.
-
@prismcnd said:
Confirmed all files are in the proper placement. works fine without the "libfredo.rb" file, but with it as soon as i load sketchup and first action is right-click on sang all right click options are greyed out
Could you use the following code in the Ruby console (copy & paste it):
l=[];ObjectSpace.each_object {|x| l.push x if x.class==UI::Command } ; l.lengthThis displays the number of Command objects.
After enabling LibFredo6 3.4c, check in the Ruby console BEFORE you right click and then AFTER.
Thanks
Fredo
-
Some other plugin can still add to that - so it would not be an idication of FredoLib is the cause. To determine that one must disabled FredoLib and see if you still get an increase - if so, then there's another plugin doing this.
-
I get 332 before AND 332 afterwards...
How about making an observer script that watches the number of commands a la code snippet, and when it approaches /reaches 1000 it pops up a dialog warning you that you have too many commands loaded and might like to sort out your plugins or suffer 'grayed' context-menu items...
It would be nice it it could purge unused commands... but how ? ObjectSpace.garbage_collect ? -
@tig said:
I get 332 before AND 332 afterwards...
How about making an observer script that watches the number of commands a la code snippet, and when it approaches /reaches 1000 it pops up a dialog warning you that you have too many commands loaded and might like to sort out your plugins or suffer 'grayed' context-menu items...
It would be nice it it could purge unused commands... but how ? ObjectSpace.garbage_collect ?The normal behavior should be that Commands objects are released as any othe Ruby object (This is what I thought by the way). From what jhauswirth reported, it seems that each UI::Command creates an underlying Windows static object which might itself not be released, even if the UI::Command object would be garbaged out by Ruby.
Fredo
Advertisement