

that being said if i could streamline this (draw trim extrude boolean) process with a script or different workflow please let me know. I think this is a problem not with Moi but with the workflow i'm used to. obj which by the way Moi does a wonderful job with n-gons i found my excuse, i'm happy again! now if i reverse my thought process, create in Moi then export to SK via. This gives me the results i want and is a lot more flexible than SK. here's what i've come up with: cube draw line or other shape on side boolean union if extrusion is inward and not touching existing edge or extrusion is outward boolean difference if extrusion is inward and touching existing edge. for now i have played a little to see if i could accomplish this functionality for myself somehow.
#SKETCHUP 17 VS 18 SOFTWARE#
Thanks for the consideration Michael, i definatly think this type of feature would sell alot of software for you (not to say that it won't sell great now). I have added Sketchup file I/O to the wiki wishlist. Well, if you buy it, it makes it more likely that I will be able to stay in business and eventually be able to handle your request instead of going out of business! :) > I don't want to offend, I love Moi, i'm just having a hard time to find an Sorry! Unfortunately things that take a lot of work will take time before they can be implemented. I don't expect to be able to complete that work anytime too soon. To make the import come into MoI I would probably have to implement polygon mesh objects as another type of object you could create and edit inside of MoI, which is a considerable amount of work especially trying to integrate them with commands like trimming and booleans, etc. Rhino works with both polygon data and NURBS data, that is one reason why a Sketchup import into Rhino was not quite as difficult.
#SKETCHUP 17 VS 18 CODE#
It looks like the Sketchup guys send out some I/O helper code to some companies who request it.īut the main difficulty that I mentioned earlier is still there - Sketchup uses polygons and MoI uses NURBS and does not currently work with polygon mesh objects (other than at export time).

Yup, it is definitely possible - I'm sorry if I gave the impression that it was impossible, that's not what I meant to say earlier, I mean to say that there were issues that make it somewhat difficult, taking a fair amount of work to make it happen. and maybe not that difficult if one could borrow the rhino code. What is needed here is a entity identifier which include the "path" to get to the entity, so it truly represents a single unique entity in terms of the display.> so. As I drill down through the database and think I am pointed at a single, unqiue entity, I am often pointed to an entity in a component definition, which, if the component is used more than once may be in hidden instances of the same component, instances of the component which are on layers which are off, as well as in an instance which is visible. However, as I write this I see that part of the problem is what is meant by an entity. The last two are pie-in-the-sky, but the first one would be a useful function. However, it would be nice if they added 1 to 3 of these new functions:Įntity.is_visible? - not hidden, and not on a layer which is hidden (including groups and sub-components which are hidden or on layers which are hidden)Įntity.is_in_current_view - is_visible? and also is visible in current camera viewĮntity.is_obstructed - is visible? but is behind something else which is not transparent. MartinRinehart wrote:Any reason not to declare visible? a bug?Īt this point, if they some changed what it meant, it would break any scripts which were using it to mean "not hidden". #printf("is_enitity_visible_in_sketchup: %s return true\n", )

# Layer0 is only invisible at the top level #printf("is_enitity_visible_in_sketchup: %s\n", ) In included both entity.hidden? and !entity.visible? - which is probably redundant.Ĭode: Select all def is_enitity_visible_in_sketchup(entity) It gets tricky because an entity in a nested group/component is invisible of any of the layers of the parents is off, (except for Layer0 which is always on in a component or group even if it is off at the top level). I wrote this routine to determine if an entity is truly visible. If e is on an invisible layer I'd like e.visible? to report false, no? MartinRinehart wrote:Did a quick test: e.visible? reports true when e.hidden? reports false.
