Full Version: V4 Wish List

Show messages:  1-19  …  160-179  180-199  200-219  220-239  240-259  260-279  280-299  …  560-575

Hi Burr, that is actually possible now I just removed some of the quick links to it in the original forum streamlining.

But you can still access that forum functionality by going to Options on the top bar and then "Relationships" in the left side menu.

Search on the user name, then click on the name in the list and you can set that user's messages to be ignored.

- Michael

---

Thanks Michael.....very useful tip!

---

Bingo. Works perfectly!

---

Shhh. This is a test to see if in fact Burrman has relegated me to his discard pile.... :-)

---

Lol..... never!

---

Michael,

just a small request (probably won't be too hard). I wouldn't having larger windows for layer naming, or possibly make it possible to drag the window to larger. Sometimes (often) our files name are such that I can't see the layer's entire name.

Cheers.

Image Attachments:
Capture.JPG 

---

Hi Sebastian, I'll see about making it resizeable in v4.

For the moment you can get what you need by editing the UI files though, go to the /ui sub-folder and edit the file named EditNameDialog.htm in a text editor.

The text field is on line number 30 which currently has:

				<td><input id="nameinput" size="32" style="width:auto;"></td>

If you change the size="32" to something larger that will give you more space, like if you make it size="64" that will have room for 64 characters.

- Michael

---

Cheers Michael that worked :)

---

Hi Sebastian, also I was able to tweak things for v4 to make the edit name dialog resizable in width by dragging the window edges. So in v4 you'll be able to just drag it to whatever width you prefer and it will remember that new width.

- Michael

---

Awesome! Awaiting the beta... :D

---

Might it be reasonably convenient to implement OLE DB in version 4 and assign every MOI object a unique identifier to link to external databases?
Either way, MOI3D is the greatest.

-- MindSet

---

Hi MindSet, I'm sorry but I'm not already familiar with OLE DB and so it would take too much time to research it and figure out how to work with it.

Each object in MoI is already assigned a unique UUID though, and it is accessible to script by the .id property which returns it as a string.

Maybe the OpenNURBS library would be useful to you, it's available from https://www.rhino3d.com/opennurbs , using that library you could open .3dm files saved by MoI and access the objects with their UUIDs from your own program.

- Michael

---

Just to things:
- 64 bit support, so I can really load big files.
- Block / Instance support, as this is essential in my work.. however I wonder if instances exist in output formats like OBJ (They exist in LWO).

---

<<"64 bits"

it's for that V4 is created! :)

---

Hi Robert, yes 64-bit is the main goal of the rewrite for v4, so that will be in the first beta release.

Instancing is high on my radar to work on during the v4 beta period, but it is a big area overall especially including data transfer like you mention. OBJ format does not have any concept of instancing in it. LWO format in its original form I don't think has it either actually, I can't find it mentioned here: http://static.lightwave3d.com/sdk/2015/html/filefmts/lwo2.html it's possible that it's implemented as an extension in it that's not part of the old public spec though. Trying to deal with undocumented types of data can be very time consuming.

It might be possible for FBX and SKP format for current export types. It could be a good reason to implement some additional formats like Collada.

Something that's such a large area isn't too likely to get implemented all in one single go though, it's more likely that it will come in stages with a focus on the UI for working with the instancing in MoI only at first before trying to tackle import/export to other formats.

- Michael

---

Hi Michael,

While I have not personally tested it, seemingly whether by ADO or OLE DB, the Database Connection can be hosted by the JavaScript interpreter.
https://www.google.com/#q=ole+db+javascript
https://www.google.com/#q=connect+html+page+to+sql+server+database+using+javascript

Does anyone on the forum have direct experience with this?

Maybe your V4 could expose the objects' unique UUID and provide a method that uses it as a parameter to select the object.
Because SQL Server has a hierarchy data type, grouping could be managed externally.
Of course SQL naturally treats all data as Boolean sets.
I would be willing to help with the SQL code, i.e. Stored Procedures, etc..

-- MindSet

---

Hi Mindset,

re:
> Maybe your V4 could expose the objects' unique UUID and provide a method that uses
> it as a parameter to select the object.

This is actually possible in v3 currently - in script there's an .id property on objects that returns the object's UUID in string form.

The reverse way to look up an object given the UUID is provided by the findObject() method on moi.geometryDatabase, it's used like this:
var obj = moi.geometryDatabase.findObject( id );

- Michael

---

Yea Michael,

I'll give it a try and report back!!

Thanks,
-- MindSet

---

https://en.wikipedia.org/wiki/Universally_unique_identifier

---

Hi Michael.

What's the compatibility degree of the upcoming V4 with the current latest V3 ?

More in depth :

1) Scripts.
The new API core (if there is a new one) will be backward compatible with the current API ?
All the Scripts written for V3 will continue to work properly on V4 ?

2) .3dm file format
Moi V4 will use by default the Rhino 5 format instead of Rhino 4 ?

3) Html files.
The new V4 will accept all custom html files used to customize V3's UI ?

4) Shortcuts
Can I use with V4 all the hotkey setup that I currently use for V3 ?

Thanks a lot and have a nice day.

---

Show messages:  1-19  …  160-179  180-199  200-219  220-239  240-259  260-279  280-299  …  560-575