[Plugin] RichSection V0.5.8 UPDATED march 2015
-
Thanks
-
god please you
-
@rich o brien said:
Indigo respect Section Cuts
Rich, can you confirm that Indigo works with this plugin?
Then I guess I'd like to know how Indigo can do it and other cannot.
-
pgarmyn,
Tour de force!
Videos look marvelous too... however, is it working properly for everybody else?
So far I'm getting no result from the plugin.
It makes cuts and shows the dialog box, but never generated sections with materials.
IOW it is working like native SU section tool, although it does generate automatically named scenes.
I'm on Win7, Dell XPS8500, Intel Corei7-3770 3.4GHz, 12GB RAM, SketchUp8.
Any help? -
Great plugin!
Is it possible for different solids/groups/components to be assigned different hatch properties so that you can show different hatch patterns with the same section cut?? Like Revit's section box?
That would be awesome...
Joel
-
This plugin is exactly what I need!
-
@takesh h said:
pgarmyn,
Tour de force!
Videos look marvelous too... however, is it working properly for everybody else?
So far I'm getting no result from the plugin.....
Any help?It should work on SU8. (It works for me)
You are the first after 160 downloads. Are there other people having problems?Do you use components or groups? Are they closed in the sectionplan?
Test it with a Solid without changing any parameter in the dialog box?Is there any error on the Ruby panel?
-
@ivreich said:
Great plugin!
Is it possible for different solids/groups/components to be assigned different hatch properties so that you can show different hatch patterns with the same section cut?? Like Revit's section box?
That would be awesome...
Joel
YES the 2nd video is showing that
Use RichSection materials 'by layer' or 'by nature' or a combination.
Every RichSection can also have different section materials, by using a different 'prefix'
-
-
Hello,
i install the plugin but it doesn't appear any where , i searched in toolbar menu , any idea ?
I am using sketchup 2013. -
@micione said:
Report a conflict with "offset.rb."
attached file.Ok, thanks. I will try to fix that. It will take some time....
-
@doush-007 said:
Hello,
i install the plugin but it doesn't appear any where , i searched in toolbar menu , any idea ?
I am using sketchup 2013.A new plugin must be activated in the menu 'window/preferences',
a panel opens, select 'extensions' and activate 'RichSection'. -
thanks a lot
-
@micione said:
Report a conflict with "offset.rb."
attached file.Offset.rb is not a standalone plugin (Can be called by other plugins). It is from Rick Wilson, created in 2004.
What's happening How do you know there is a conflict
What other plugin is using offset.rb ? (Probably anther plugin from Rick Wilson) -
Because your code is all encrypted we don't know what it does.
If it has any 'offset; methods within it that are not encapsulated in your module/class methods, then your 'offset()' method might well clash with the bald scripted 'offet.rb' by RickW, if users have that loading with other scripts.
Your code must not interfere with base class/module/methods or other's scripts that load as helpers - these are things like offset.rb, progressbar.rb and so on... It's easy enough to recast your own versions within your own modules so there is no overlap with other scripts... -
@tig said:
Because your code is all encrypted we don't know what it does.
If it has any 'offset; methods within it that are not encapsulated in your module/class methods, then your 'offset()' method might well clash with the bald scripted 'offet.rb' by RickW, if users have that loading with other scripts.
Your code must not interfere with base class/module/methods or other's scripts that load as helpers - these are things like offset.rb, progressbar.rb and so on... It's easy enough to recast your own versions within your own modules so there is no overlap with other scripts...About my code:
- Every method, variable, ... is declared within module PiGa ; module RSection ; end ; end
- No basic classes or modified or extended.
And this is the case for the loader PiGa_RichSection.rb, and the main ruby RichSection.rbs
That wasn't yet good practice in 2004 (Looking in code of offset.rb)
I scanned my code : there is no method 'offset' or anything else named 'offset'So, if there is something The problem is not there.
Please, micione tell me....
What's happening ? How do you know there is a conflict ?
What other plugin is using offset.rb ? (Probably anther plugin from Rick Wilson) -
pgarmyn,
"offset.rb" is used by other tools of Rick Wilson (eg "windowizer").
What happens:
Your tool applies the first section, then it stops, stuck.
Any attempt to use the "move tool" on the section, it causes BugSplat.Only by removing "offset.rb" your tool starts working again.
In order to identify the conflict, must be eliminated (one by one) all installed plugins. And this is what I did.
I hope I was helpful.P.S. perhaps seek the advice of Rick Wilson?
-
@micione said:
pgarmyn,
"offset.rb" is used by other tools of Rick Wilson (eg "windowizer").....
Thanks
I will test it out. Tomorrow -
@unknownuser said:
A futur hit for sure!
When you say Demo, will be commercial at the end ?Maybee commercial... . But I will also keep a FREE version .
Until March 2014, everybody can have the full 'DEMO'(Thanks for the correction Bob James)
As 'RichSections' are standard SU-groups, they only need the plugin for update. -
The issue might be that
offset.rb
[ill advisedly] adds a new method toArray.offset(distance)
* this clashes with thePoint3d.offset(vector, distance)
because an Array of three values [x,y,z] can be offset just as it it were a Point3d, but the native method is expecting a Vector3d [or an Array of three [xv,yv,zv]] and an optional second argument of a distance that overrides the vector's length...*In my copy of
offset.rb
I have renamed it asoffsetArray(dist)
to avoid the clash [it's never used anyway!].So to avoid clashes with the
offset.rb
methodArray.offset()
never use.offset()
on point that is expressed as an Array - make that array into a Point3d before the offset is applied, then the clash is avoided.
So it should be
point=Geom::Point3d.new(0,1,2)
[or...new([0,1,2])
]
then
point.offset(vector)
or in one step
Geom::Point3d.new([0,1,2]).offset(vector)
BUT NEVER
[0,1,2].offset(vector)
or
pt=[1,2,3] pt.offset(vector)
Advertisement