Full Version: How do you reference a specific object in Moi3D scripting?

Show messages: All  1-6  7-13

Hi Elang,

re:
> How can I assign a name to this line immediately after it is created, without manually
> selecting it first, so that I can easily refer to it later in the script?

The preferred way to do that is to retrieve the object reference when it is created.

There are 2 ways that geometry factories can be used, one is by hooking up UI controls to factory inputs, triggering a factory.update() when the UI controls are changed, and then calling factory.commit() at the end. This is the way that most commands in MOI work since they have UI controls.

That way handles various things automatically like removing any previously generated objects from the geometry database and inserting the newly generated ones into the geometry database so they are displayed, clearing them out if the command is canceled, and other similar stuff.

Your example here is not like that:

var linefactory = moi.command.createFactory( 'line' );
linefactory.setInput( 0, moi.vectorMath.createPoint( 0,0,0 ) );
linefactory.setInput( 1, moi.vectorMath.createPoint( 10,10,10 ) );
linefactory.commit();

The regular line command does a lot more than that, it sets up a point picker and spins an event loop waiting for the user to click a point with the mouse or type in the coordinates of the point, set a checkbox option, etc...

Your script here just wants to generate a line between 2 specific points, not collected from user input and no UI options to be set. Perhaps you don't even want the line to even be displayed and just use it as a building block to be sent in as an input to another factory.

For that case it is better to use the 2nd method of using a geometry factory, the factory.calculate() function. That will return an object list of what the factory generated and doesn't do anything else. The result will not even be displayed yet since it will be a "loose object" and not inserted into the Geometry Database yet, you can do that manually with moi.geometryDatabase.addObject().

Using factory.calculate() and getting the line object reference for use later on in the script is like this:

var linefactory = moi.command.createFactory( 'line' );
linefactory.setInput( 0, moi.vectorMath.createPoint( 0,0,0 ) );
linefactory.setInput( 1, moi.vectorMath.createPoint( 10,10,10 ) );
var result_object_list = linefactory.calculate();
var line = result_object_list.item(0);

You could then assign a name using by doing
line.name = 'the line';
but you wouldn't normally do that as a lookup method later on, you would pass in the line variable that is an object reference.


It is possible to collect the output using the update()/commit()/cancel() method, to do that you would need to make sure factory.update() is called, then use factory.getCreatedObjects() before the .commit() :

var linefactory = moi.command.createFactory( 'line' );
linefactory.setInput( 0, moi.vectorMath.createPoint( 0,0,0 ) );
linefactory.setInput( 1, moi.vectorMath.createPoint( 10,10,10 ) );
linefactory.update();
var result_object_list = linefactory.getCreatedObjects();
linefactory.commit();
var line = result_object_list.item(0);
line.name = 'the line';

But note that the line will be in the geometry database and so displayed in the viewports (the viewports draw the contents of the geometry database, they don't draw "loose objects" that are only referenced by script code and not listed in the geometry database).

If your script is generating the line as a building block with specific inputs instead of using a pointpicker the calculate() method is preferred.

Hope this makes sense, let me know if anything here isn't clear.

- Michael

---

Hi Michael,

Thank you very much for taking the time to write such a detailed explanation. It makes much more sense to me now.

I think I understand the distinction between using `update()/commit()` for interactive commands and using `calculate()` for programmatically generating geometry. I also understand why obtaining and keeping the object reference is the preferred approach.

I would like to spend some time studying these concepts and experimenting with both approaches before asking any further questions. I'm sure I'll learn much more by trying them myself first.

Earlier you asked what I was actually trying to accomplish. My long-term goal is to build procedural scripts that generate many objects and perform a sequence of operations on them. Rather than creating just one or two objects, a script may eventually generate dozens of intermediate and final objects before reaching the final result.

Once I have explored these concepts a bit more, I'll come back with a more concrete example of that workflow. I think it will make my questions much clearer.

Thank you again for your patience and for sharing your knowledge. I really appreciate your guidance, and I'll be back on the forum soon after I've had some time to experiment.

Best regards,

- Elang

---

Hi Michael,

I've attached a script that I've been working on as part of an R&D project at the company where I work. We have three MoI3D V4 licenses, all of which are used by our design and engineering team.

The goal of this script is to automate the creation of production box designs for our souvenir products. The idea is simple: the user enters the overall bounding box dimensions of a souvenir, and the script automatically generates the corresponding box design.





If you have some time, I'd really appreciate it if you could take a look and share your comments. Also, if you notice that I'm still approaching things with the wrong paradigm (as you pointed out in one of my previous posts) please don't hesitate to correct me. I'd much rather learn the proper way than continue building on a flawed approach.

My hope is that this tool will reduce the engineering time required for each box design by around 10–20 minutes, making the workflow more efficient for our team.

Thank you very much for your continued support and for all the knowledge you've shared with the MoI community over the years. It is genuinely appreciated.

Best regards,

- Elang

Attachments:
-AutoBox02.htm
-AutoBox02.js

Image Attachments:
2026-07-23_155110.jpg  2026-07-23_155543.jpg 

---

Hi Elang,

re:
> If you have some time, I'd really appreciate it if you could take a look and share your
> comments. Also, if you notice that I'm still approaching things with the wrong paradigm
> (as you pointed out in one of my previous posts) please don't hesitate to correct me.
> I'd much rather learn the proper way than continue building on a flawed approach.

It looks good to me! Some minor things in the .htm file:

The <link rel="stylesheet" href="moi://ui/moi.css" type="text/css"> can be removed, it isn't needed anymore starting with MoI version 3. Same with xmlns:moi in the <html>.

In the <head> you can put in a <style> with some style rules and then all the individual inline style="" and align="" attributes can be removed, see attached.

- Michael

Attachments:
-AutoBox02_styles.htm

---

Hi Michael,

Thank you very much for pointing out the `.htm` documentation. I'll definitely take a look at it later.

For now, I think I may have found a bug related to the bounding box dimensions.

I wrote this simple script to retrieve the bounding box of the selected object(s). However, when I displayed the values using `moi.ui.alert()`, the reported dimensions did not match the X/Y/Z size shown in the Object Info panel.

Here is the script:

function excercise_06()
{
	var rnd = moi.geometryDatabase.getSelectedObjects();
	var bbox = rnd.getBoundingBox();

	moi.ui.alert(
		'X Length : ' + bbox.xLength +
		'Y Length : ' + bbox.yLength +
		'Z Length : ' + bbox.zLength
		);
}

excercise_06();

In the screenshot below, you can see that the X dimension reported by `bbox.xLength` differs from the X Size shown in the Object Info panel.

Am I misunderstanding what `getBoundingBox()` returns, or could this be a bug? I've attached the 'problematic' 3dm file.



Thank you very much in advance for your attention.

- Elang

Attachments:
Plaque.3dm

Image Attachments:
2026-07-24_110041.jpg 

---

Hi Elang, since getting a precise minimal bounding box can be a time consuming calculation there are various types of approximations.

The one in the object info panel is based off of the display mesh. If you click on it to open the "Edit size" menu it will do a more accurate solver based calculation in the menu.

The one used by ObjectList.getBoundingBox() is quick to calculate and uses the bounds of surface control points. It can be larger than the accurate bounding box.

Do this if you want a "tight" bounding box:

function excercise_06()
{
	var rnd = moi.geometryDatabase.getSelectedObjects();
	var bbox = rnd.getHighAccuracyBoundingBox();

	moi.ui.alert(
		'X Length : ' + moi.ui.formatCoordinate(bbox.xLength) +
		' Y Length : ' + moi.ui.formatCoordinate(bbox.yLength) +
		' Z Length : ' + moi.ui.formatCoordinate(bbox.zLength)
		);
}

excercise_06();

---

Understood... Thank you very much, Michael!

---

Show messages: All  1-6  7-13