[Plugin] RichSection V0.5.8 UPDATED march 2015

pgarmyn

Thanks...I managed to get both material names and layer names working (apparently I can't use default material names straight from the SU library; I have to change them for them to work), but I still don't understand the difference between the two richsection options highlighted in the attached image:
Thanks!
Joel

It's a matter of priority
Supposing

Model : you used layers L1 and L2
Model : you applied the following materials to groups and components : N1 and N2
Model : Group1 in layer L1 and material N1 (assignd to the group)
Model : Group2 in layer L2 and material N2 (assignd to the group)

First case :

Model : existing materials in library 'in model' : #L1,#N1,#N2....
Model : NOT existing materials in library 'in model' : #L2
RS-options : prefix = #
RS-options : default material = #default
RS-options : section material = prefix+layername, prefix+materialname, default
RS section materials group1 (L1,N1) : #L1 (priority for prefix+layername)
RS section materials group2 (L2,N2) : #N2 (#L2 doen't exist)
2nd case :
RS-options and model as before, except:
RS-options : section material = prefix+materialname, prefix+layername, default
RS section materials group1 (L1,N1) : #N1 (priority for prefix+materialname)
RS section materials group2 (L2,N2) : #N2

Like for standard materials : nested groups can inherit the RichSection-material of a parent group

pgarmyn

@arcad-uk said:

@Pgarmyn

My missing faces were in repeated components and should have formed a 50 x 100mm face in a rectangular box, so size wasn't the issue. The final solution in that case was to delete the failing group and create a fresh box. TIG spent time updating his plug using some of my models but I can still get face errors with abutting groups for no obvious reason. If you and TIG are both seeing this then you may need to get Trimble to look at the API.

My experience is that SU (and his ruby method 'intersect_with') can't create an intersection-face if:

small faces; small is relative : it depends of the extends of the model
to many entities (edges, faces) in the same context (context = in the same group or component)
to many (complex) loops to create in the same context

ArCAD-UK, for the repeated 'small' components, does SU recognizes them as a solid? What are the dimensions of the model?
Maybee jou can send me the problematic skp-file (private if necessary, I will only use it for testing....)

mladen90

This is unbelivable! Thank you soo much pgarmyn for sharing this.
It is just what i have been searching for for years. Now sketchup could be finally used as a proper drawing tool, without worrying are cetions up to date, visible to other scenes etc.

I downloaded it yesterday via sketchucation plugin manager and it says it's expired back in march 2014?.
https://dl.dropboxusercontent.com/u/35033714/expired.jpg

I thought i should report this.
Thank you again pgarmyn!

pgarmyn

@mladen90 said:

This is unbelivable! Thank you soo much pgarmyn for sharing this.
It is just what i have been searching for for years. Now sketchup could be finally used as a proper drawing tool, without worrying are cetions up to date, visible to other scenes etc.

I downloaded it yesterday via sketchucation plugin manager and it says it's expired back in march 2014?.
https://dl.dropboxusercontent.com/u/35033714/expired.jpg

I thought i should report this.
Thank you again pgarmyn!

Yes, thanks for reporting this.
Indeed this (full) DEMO expires on 1 march 2014. I will replace it by a free (limited) and a FULL version. But strange that you have this message.
Are you living in the future Did you changed the date of your computer
Is the licence-file in de directory (plugin/PiGa_RichSection/RichSectionLicense.rb)

Let me know....

mladen90

I haven't change my date on PC.
I have resources folder, RichSection.rbs and RichSectionLicence.rb in folder you mentioned.

I have had experienced similar thing with RealSection, but that was common problem ( It truly had expired and nobody continued to work on it). I guess RichSection doesn't use any of RealSections libs? Could this be the problem?

Thanks for your quick reply.

pgarmyn

New video added to the first post...

pgarmyn

@mladen90 said:

I haven't change my date on PC.
I have resources folder, RichSection.rbs and RichSectionLicence.rb in folder you mentioned.

I have had experienced similar thing with RealSection, but that was common problem ( It truly had expired and nobody continued to work on it). I guess RichSection doesn't use any of RealSections libs? Could this be the problem?

Thanks for your quick reply.

Strange, you are the first having this problem after 380 downloads!
The RichSection plugin can't interfere with other plugins.
When did you got this message. Directly after putting the first RichSection? .... When updating?

Can you switch 'on' logging in the menu (plugins/RichSection/settings) and open the ruby console.
What is printed in the Ruby console, when you place a RichSection...

mladen90

Wow! Astonishing new video. Just what I imagined it cold be done with RichS.

Considering expiration problem. I did enable logging.
It happens when I try to make real section (via menu-bar or right click).

Here is the log:

---------------------------onElemAdd : Sketchup::SectionPlane
toolRScreate_part2 :
toolRScreate_part2: createRS :

Plugin: RichSection
Copyright: 2013X, All rights reserved for RichSection plugin : Name, code and functionality are the intellectual property of the author. Distribution, reproduction or integration of code or functionality, even partly, is only permitted with the explicit permission of the author
Version: V00.01-2013.11.17-18:00 DEMO_________________________
:
proc createRichSection :
licensefile found : C:/Program Files (x86)/SketchUp/SketchUp 2013/Plugins/PiGa_RichSection/RichSectionLicense.rb
licensed for computer: : any
licensed for MAC-adress: : any
licensed for version: : V00.01-2014.11.17-20:00 DEMO
licensed until: : Sat Mar 01 00:00:00 UTC 2014
license type: : DEMO, valid until 2014-03-01
license to (name): : Everybody
license to (mail): :
key1: : SoftwarekeyForTheDemoLicenseUntil-2014-03-01
key2: : fz1njmunn7pfa45t9o1bv0yatdvaln7wvrpl8oitml3301vizcszy0cjyepk1r14mkve
Faces : 12
Instances : 1
Definitions : 1
@modelcomplexity : 0
thisRSversion = V00.01-2014.11.17-20:00 DEMO? : V00.01-2014.11.17-20:00 DEMO
License VALID :

I hope that this help.

pomelo3d

thank you very much for this fantastic plugin.
On my computer, now shows the same error message, because the plugin expired.
you can fix that? thank you very much

ArCAD-UK

I was about to check the models TIG worked with and got the same EXPIRED DEMO message.

pilou

@unknownuser said:

The RichSection plugin can't interfere with other plugins.

But sems at least 2 plugins "windowizer.rb" and "wxSU.rb" bugsplat it!

pgarmyn

@unknownuser said:

But sems at least 2 plugins "windowizer.rb" and "wxSU.rb" bugsplat it!

As i said before, every method, variable in the RichSection plugin is declared in the RichSection namespace.

As Windowizer ads a base method and extends SU classes, it interfears with ALL the SU plugins!
I didn't look at the wxSU code.....

emerald15

@pgarmyn said:

@emerald15 said:

I use RichSection to great effect. I really like all the additional optional colours, line types & infills.

May we see the result

Here's the section part of the drawing. Having all the none visible objects shown in dashed lines really helped.

section example.pdf

pgarmyn

[highlight=#ffff00:e4viin5e]:bounce: UPDATED, but probably not yet on the plugin store. (Need time to find out if I can do this by myself... ) [/highlight:e4viin5e]

pgarmyn

@emerald15

Thanks for sharing your work.
You are the first using projected information
Maybee you have to use a non white section-material

Rich O Brien

@P

You need help updating store?

pgarmyn

@Rich
Thanks for the quick reply.
TIG gave me alreardy a very complete explanation on the Sketchucation-tools-page,
But I will need to find some time to work it out.... .
Where can I find the Authors' Guide.

TIG

@pgarmyn said:

@Rich
Thanks for the quick reply.
TIG gave me alreardy a very complete explanation on the Sketchucation-tools-page,
But I will need to find some time to work it out.... .
Where can I find the Authors' Guide.

http://sketchucation.com/forums/viewforum.php?f=382
First sticky: http://sketchucation.com/forums/viewtopic.php?p=475671#p475671

ArCAD-UK

Had a play tonight. Just some thoughts:

I still maintain creating two scenes is unnecessary. If there are a lot of plans and sections then the screen soon becomes cluttered with tabs. It is easy and less confusing to click on the projecting scene and then "Display Section Planes" for editing.
I know why you create a Style for each section but allowing selection from [user] styles generated within SU may be easier to manage. I usually only have one or two cut styles and I note you have two for each section e.g. #001 AND #001P
There should be the option to use SU's default material rather than the default created by Rich Section
I'm not a fan of raster hatches, but they are easy enough to Purge. I don't know what other's feel but some may prefer to load them as an option?
Would an additional layer "__Profiles" which had just the outlines of the RS cut be possible so that they remain visible when turning off individual entity layers?

pgarmyn

@arcad-uk said:

Had a play tonight. Just some thoughts: 1 2 3....

Extending Sketchup with Ruby is not as
"driving a car without a steering wheel"
but some controls are missing

The SU ruby API has no (direct) method to create, activate, hide or show a sectionplan. some control is possible using a Scene or a Style. [highlight=#ffff00:2itt6uzf]Thus, I NEED THOSE TWO SCENES AND STYLES[/highlight:2itt6uzf], to save my settings, to switch things on/off... .

Many methods to control a 'scene' or a 'style' are missing. A workaround to create a style with the sectionplane activated is to load a style from a file, (a file created before with visibility and active sectionplan as needed) and update it with the active style-settings. What complicates the whole thing is that some methods (like loading a style from a file) can't be in the undo DB. Roughly, my plugin is 30% core code, 30% input & data management and 30% workaround.
2 see 1
3. The shortest workaround is that YOU save YOUR default material (white, red, hached or not), and select it as default in the RS-settings. You can also (at your ouwn risk) eliminate or replace the bitmaps in plugins/PiGa_RichSection/resources/mat. They are loaded at the creation of the first RS. But the plugin needs at least a #default.png (bitmaps applied with dim. 30x30cm). I plan to replace the bitmaps by a .skm library, but you keep me busy with ....
4. I have tons of ring and bels to install, but first I have to upload a working version to the plugin store.