Topics created by medeek

Version 0.8.0 - 03.14.2021

Created the Medeek Engineering Plugin, utilizing SketchUp's Ruby API (BETA release).

I haven't paid much attention to this plugin for about 8 months as I have been so busy updating all of the other plugins (Wall, Truss, Foundation and Electrical). When I get some more time I will get back to work on the matrix analysis engine that is required for the calculation module. For now you should be able to add loads and supports to beams created with the beam module of the Medeek Wall plugin.

The plugin is very much in BETA right now, however I wanted to at least get it out so people can start playing with the load and support tools and give me any feedback they might have.

The BETA/Trial version of the plugin can be downloaded here:

http://design.medeek.com/resources/medeekengineeringplugin.pl

Note, that you cannot purchase this plugin yet. I will not enable purchasing until I have completed the calculation module and brought it out of BETA status.

Version 0.9.9t - 11.19.2024

Added the "Open Web" floor family (RedBuilt™: Red-L, Red-M, Red-S, Red-M, Red-H). Added the following TriForce Open Joists: OJ3-14, OJ4-14, OJ3-16, OJ4-16. Added the "Steel Truss" floor family (Nucor®: K-Series). Added a removal parameter for sill plates.

floor_su225_800.jpg

floor_su226_800.jpg

@juju said:

The design and airflow calculations and such should be done by the appointed Mechanical Engineer. Until you’re ready to do that deep dive rather produce a tool that can be used for the layout, auto sense and insert the correct item at turns and has a variety of the diffusers / split units (typical) / grilles / whatever that can be used.

That is kind of my thinking, start with the basic layout (3D model) first, the calcs can always be added to the program.

Version 1.2.4 - 08.04.2024

Added a duplicate title block assembly check to the regen module for all title blocks. Enabled wall sheathing 2 within the Medeek Estimating Module for wall assemblies.

Version 1.4.7 - 07.18.2024

Added combined "smoke/CO" detectors under safety devices. Updated the Legend tool to include combined smoke/CO devices.

elec_su257_800.jpg

The included device in the smoke/CO library is a KIDDE 30CUDR. Just bought this one yesterday and modeled it this morning.

https://www.amazon.com/dp/B0CX664SNZ

Note the 2D symbol text for this type of device is "SC".

How do you 'know' for sure that setting the definition's attribute fails ?
You give insufficient detail.
If you use get_attribute() on the exact same definition [or instance.definition] you used set_attribute() on, then it should work.

Make sure the attribute-dictionary-name and the key are exactly the same in both cases, and that you have a default value set up too - like result = t_def.get_attribute(lib, 'trussfamily', 'WTF!').
If result == @Trussfamily it's working, but if result == 'WTF!' it's not !

Make sure you have presets for the 'value' set/get @Trussfamily, and of course the ' lib' - which should be the string-name of the dictionary, e.g. lib = 'medeek_truss_eng'.

It a dictionary of that exact name doesn't exist it's made, if it exists then it's reused...
Personally I'd use dictionary name starting with an uppercase letter, and all keys in lowercase.
There's less confusion that way...

To check what's dictionaries and keys/values are attached to a definition use something like this.

if t_def.attribute_dictionaries t_def.attribute_dictionaries.each{|d| puts "DICTIONARY == #{d.name}" d.each_pair{|k, v| puts "#{k} = #{v}" } } else puts "NO DICTS !" end

Also remember that your code as we can see it ALWAYS does a commit - even if there was never an operation started.
But since we only see some of your code it's unclear if there's always an operation to be committed !
One way round that is initially to set **@**draw_status = false, then within the 'tests' use **@**draw_status = @model1.start_operation(@Model_operation, true) e.g. in if @Trusstype...
Always remembering to set in each 'test':

and then in your unshown code, for each commit you need to use:
draw_status = @model1.commit_operation if **@**draw_status
So you don't commit anything unless an operation is been started...

Most users of the plugin are SU 2018 but I've received some kickback from others so I may have to put this plan on hold and go a different direction.

Unfortunately, if the model.active_entities is not the @existinggroup.entities context and/or the array of added entities is not in that same context, then a BUgSplat! awaits...
You cannot 'cross-thread' entities across contexts...

Yes, WebDialogs are not truly modal on Mac. So you have two problems:

The code processing continues after you called wldg.show_modal. You thus have to implemnet a
callback in your Web dialog class to tell the main code when the dialog box is dismissed. Visually the web dialog appears on top but does not prevent to use other elements of the GUI.
Although the user may not do that naturally, he could technically.

It seems that HTML dialog has addressed the problem on Mac, that is blocking code and dialog box preempting the focus and events.

Fredo

See my post and PM to you on the official SketchUp Forum...

@pbacot said:

I like the stored parameters, But I'd also save the sizes. I don't want to manually make a 3080 door everytime. It's not going to be in increments, it's always going to 3080. Windows might be in increments of 2", but really for most projects there are only a few window sizes and those are plugged in repeatedly. Window head parameter would be nice, where you don't have to line up the window head each time. Actually door head too, so you don't have to set to the floor level, it automatically goes in at the correct place in relation to the floor. That's why I wondered what the 2 point placement was about. I wouln't use a tool that way, given the chance. Layout should be able to snap opening centers from a floor plan layout overlay OR use SU guides or offset from the end of walls.

I see there are two different design methods here. My initial use for this plugin was to provide windows and doors into the rough openings created by the Wall Plugin. As such the positioning of the opening is set by the wall plugin and not by this plugin or module.

However, if you are using this plugin as stand alone then the ability to position the opening and set the RO size becomes important. Also the ability to cut holes in exsitin

Two different uses. I will need to give this more thought.

Thank-you for the example and explanations.

PLusspec is still more expensive per year than Archicad and Vectorworks (and only has a fraction of their capabilities)---and if we decide not to renew, we have no software to work with.

Sell us a station, then let us decide if we want to upgrade every year. If we don't, at least we have last year's model to continue working with (if it was a stable version). There are still users producing solid work with SKP 8, and I have last year's version (20) of Archicad which I can use, if I wish, for the next 20 years at no ongoing cost.
I paid once for the licence. I own it. It is entirely my choice if I wish to upgrade to 21.

In the face of your costing hi-jacks as a BIM puppy, your glowing mea-culpas are tiresome.