Posts made by GWD

@tomb85 said:

@ladcwei said:

if the section plan goes through the components,there is no result......

There is also no result with "groups inside a group"...
@GWydouw, how do you fix this at your office when you section on components or groups-inside-a-group?
I've tried mixing the results of sectioncutface.rb and realSection together into 1 group but it gets a bit tricky and sections are no longer updateable. Is there a workaround ?

Thanks

At this moment this isn't possible. But i try to put it in the next version.

@tomb85 said:

This is really a nice plugin. I've been looking for a plugin like this for a long time.
Also many thanks for the section-hatch materials.

I don't have any experience with ruby scripting, but maybe an extra useful feature would be if you could assign a lineweight thickness to the group/material that is sectioned? Maybe trough an extra parameter that can be entered in the "define realSection material"-popup window. With this you could get a better readability of construction drawings. In the "SectionCutFace.rb"-plugin this is possible, but only for the whole section plane.
For example: walls could have thickness 5, furniture thickness 3, etc...

greetings from a fellow belgian

Good idea. I try to put this in the next version.

@schnydix said:

hi i tried aut your plugin real section
if i open the test file it works fine
but my own solids would never shown a real section i Played around with 4 hours
I make a solid right click on it and i have NO Dropdown (Arrow) menu. What make i wrong?
Win xp su8
can i make my own Hatching and rename it later in a version?

And Thank you for the great idea and the work

Yes you can make your own materials just see that the material name starts with '_'

Guy

@dan rathbun said:

@unknownuser said:

But i read something that the send_action with a code doesn't work on the mac version. Do you know if this is correct?

I believe that is correct because the platforms are built with different Automation IDs. (I'm not a Mac guy, but I think the Mac IDs are strings, rather than integers, as on Windows.)

What we need is a cross-platform Sketchup.send_action() string, or these keys added to the RenderingOptions hash.

I agree. What we need is that everything what you can do with SU is also supported in the API. I don't know why there are some parts that aren't supported (sectionplanes, Export 2D graphic (dxf), ...)

@dan rathbun said:

I looked thru the SU Registry settings and it is not there.

We would expect these settings to be kept in the model's and page's RenderingOptions hash, but I dont see it there either.

PC ONLY:

Toggle "Display Section Planes"
Sketchup.send_action(21347)

Toggle "Display Section Cuts"
Sketchup.send_action(21348)

These are equivalent to telling the Windows API to perform the default action on the control (toolbar button in this case,) with the given Automation ID.

For a query.. it might be possible to use a call thru Win32API class, to get the checked state of the button. (The toolbar window name is "Sections" for US-en, and it's Automation ID is 477.)

Or, you might get the View menu object and check the checked states of the menu items, again via a Win32API call.

Thanks Dan the toggle is good enough for me. But i read something that the send_action with a code doesn't work on the mac version. Do you know if this is correct?

Is there a way to control the 'Display Section Cuts' with ruby?

@dave r said:

Thanks. I'll give it a try.

I wonder why it isn't possible for your script to put the face on the section plane in exactly the right spot. TIG's SectionCutFace seems to do it exactly right every time.

Dave, now it's in the right spot like TIG's SectionCutFace. But also TIG plugin is moved a little bit.

@dave r said:

That seems to work now although, curiously, the faces don't align accurately with the section cut. See the attached model and zoom in close to the corners. And it seems the materials must already be defined in the model before starting to create the realSections. Is that right? I added the material called _Blue after creating the realSections. The name shows up in the list for defining materials but after selecting it for one group and updating the realSections the face disappeared. When I set it back to the brownish color, the face was recreated.

Problem solved in v0.5
There will always be a very little displacement because it's impossible to put a face on the sectionplane without display problems.

@dave r said:

That seems to work now although, curiously, the faces don't align accurately with the section cut. See the attached model and zoom in close to the corners. And it seems the materials must already be defined in the model before starting to create the realSections. Is that right? I added the material called _Blue after creating the realSections. The name shows up in the list for defining materials but after selecting it for one group and updating the realSections the face disappeared. When I set it back to the brownish color, the face was recreated.

That the section faces don't align is normal, because i place the faces a little before and a little behind the sectionplane. But because you work in other units the gap is to big. I try to solve the unit problem asap.

@jim said:

Is the problem because the plugin relies on Windows-specific libraries (Win32API.so) which are incompatible with Mac OS?

No plugin check if it's a PC or a MAC. But the problem should be fixed.

There was a small problem with version 0.3. This is now solved in realSection v0.4. I hope you will still enjoy realSection!
I tested it on SU7 en SU8 and it should work on both version without a problem.

@dave r said:

At Define Material

748115
> 748123

At Make realSection

Error; #<NoMethodError; undefined method `hide_Outliner_MI' for RealSections;Module>
> (eval);1722;in `updaterealSection'
> (eval);1882
> (eval);1722;in `call'
> (eval);1722

At Show realSection

748115
> 748123

At Update realSection

748115
> 748123
> Error; #<NoMethodError; undefined method `hide_Outliner_MI' for RealSections;Module>
> (eval);1722;in `updaterealSection'
> (eval);1894
> (eval);1722;in `call'
> (eval);1722

FWIW, the Outliner wasn't open to begin with.

Thanks I try to fix it asap

@dave r said:

Any chance you could actually tell us what you are doing in the video. It's difficult to read the menu items and so on due to the compression of the video.

I'm trying to follow your PDF instructions. When I choose Make realSection, I can give the section a name but there's no new layer created as stated in the instructions. I think there are enough folks having difficulty getting this to work that there must be a defect that needs to be fixed.

If I know what's going wrong then I can fix it. Can you open your ruby console when you are trying to run realSection and give me the errors that show up.

regards,

Guy

@dave r said:

Any chance you could actually tell us what you are doing in the video. It's difficult to read the menu items and so on due to the compression of the video.

what's in the video:

make a solid
right click at select 'Define realSection material'
cancel the define realSection material
create a new SU material named '_newmaterial'
right click at select 'define realSection material'
select the new created material 'newmaterial'
define a sectionplane
right click selectionplane and select 'Make realSection'

realSection is created

select solid again and define an other material
show sectionplanes
select sectionplane
right click and select 'Update realSection'

realSection is updated

edit solid
show sectionplanes
select sectionplane
right click and select 'Update realSection

realSection is updated

@ladcwei said:

I really like this plugs,however,it can't work at 7or8,waiting for its rebirth...

please give me some feedback why it's not working? It should work a SketchUp 8 english.

I made a little movie to show how realSection works:

http://www.youtube.com/watch?v=Z31yMxiYzdM

@errror404 said:

hello,

I'm trying to test this great plugin, but I'm having some dificulties:

1- I created a group (a simple solid object)
2- Then I created a texture that started with "_"
3- I assigned the material to the object using "Define realSection material"
4- I created a section plane
5- pressed "Make realSection" and gave it a name

but nothing happens... and no new layers are created?!

I'm using SketchUp 8 (free) on a windows machine (XP)

Can you send me the model?

Perhaps thearender4su plugin is not the reason
sometimes " Define real.... ", it's grey, "can't work", i mean it
sometimes " define real..." is grey, sometimes isn't, it's joking me?

but i don't know, how to make section plug worked , i mean show the materials on the section.

Can you send me the model and some screenshots of the problem?

@unclex said:

@unknownuser said:

@unclex said:

Can't Choose Materials...
[attachment=0:gu9cegbn]<!-- ia0 -->webqq_app.jpg<!-- ia0 -->[/attachment:gu9cegbn]

Did you use the demo file?
The name of the materials that you will use for the section need to start with '_' like '_concrete'
The materials are the standard SketchUp materials that are active in the model.

I see you work with SU 7, at this moment realSection won't work with v7. I hope I can fix the problem with SU 7 very soon.

thank u replied

i use SU8Pro

i can see the demo's section, but can't use it

and ur plugin can't work with thearender4su plugin

What do you mean with 'can't use it'?
What do you mean with 'can't work with thearender4su plugin'?

@dave r said:

Nice plugin. It could be very useful. I tried it on a model that someone sent to me the other day. It fixed a few things in one component but still left errors. There were a lot of errors in that component to begin with and it certainly would reduce the time required to manually fix it. Unfortunately the plugin doesn't always seem to recognize that a component is not solid. At least it doesn't recognize that the component in the attached SKP is not solid although you can easily see several problems that keep it from being considered solid.

At this moment fixSolid only work on groups not on components. I'll make it work on components to.