Full Version: Lots of unkown

Show messages:  1-4  …  25-44  45-64  65-84  85-104  105-124  125-144  145-164  …  365-372

Hi Cemortan_Tudor, I think you're maybe not targeting the point that you need?

If you start a construction line here:


And end it here:


Then you will have 4 "end" snap points available. Those 2 above where and an additional one here:


And another one here:


For what you want, you want to target these 2:


You do not want to target these 2:


There will also be a "Mid" snap available here, you don't want this one either for this particular use.


- Michael

Image Attachments:
cline_mirror1.jpg  cline_mirror2.jpg  cline_mirror3.jpg  cline_mirror4.jpg  cline_mirror5.jpg  cline_mirror6.jpg  cline_mirror7.jpg 

---

Another demo:



- Michael

---

thanks, my fault, it makes a point snap upon releasing construction lines, it's not interactive
i'll build a tool for myself

---

Message 8665.88 was deleted

---

move with hotkeys restrictions, similar to blender
move +x/y/z
wanna add one more future for softimage users )) middle click -> move with restrictions to closest bbox axis location

Attachments:
Move.js

---

It's not dangerous to name your function with the same native one ?

---

i'm replacing natives with new ones, u can read comments where and what i've changed

---

move with hotkeys restrictions, similar to blender
move +
x/y/z
s - bounding box
a - screenspace (targetFrame)

Attachments:
Move.js

---

Hi Cemortan_Tudor, so just a heads up - when you replace the standard commands you can encounter 2 problems later on when installing new versions. The first problem is the new install won't have your mods in place so you'll need to reapply them. The second one is if the standard command has any other new functionality added you will lose that new functionality if you just copy over your entire modified file rather than merging your changes in to the new one.

So you can do that if you wish but it's not recommended and you will likely encounter some problems down the road.

What I often see happening with this type of customization is that it tends to bind you to one particular MoI version for a long time and then you're not able to get bug fixes and other new things with new program version updates.

- Michael

---

O hayo !
can u make a future that disables object selection while in wireframe mode (hidden brep's or faces)

Image Attachments:
13213.png 

---

Hi Cemortan_Tudor,

re:
> can u make a future that disables object selection while in wireframe mode (hidden brep's or faces)

You can prevent an object from being selected by turning on its "locked" property, the Edit > Lock command will do that, or in the scene browser use Ctrl+click on the left status area.

Also another way you can screen objects from being selected is by turning on a selection filter. That's done in the scene browser by a Ctrl+click on the selection dot area.

- Michael

---

Intuitively that should be turned on by default

Unfortunately if any 'esc' event will cancel filters
updated
Toggle shaded mode
script:/*!Toggle shaded mode */ var breps = moi.geometryDatabase.getObjects().getBReps();var hide = true; for ( var i = 0; i < breps.length; ++i ) { var faces = breps.item(i).getFaces(); if ( i == 0 ) hide = !faces.item(0).hidden; faces.setProperty( 'hidden', hide ); } if (moi.selection.isFilterActive( 'Types', 'Edges')) moi.selection.clearSelectionFilters(); else {moi.selection.setFilter( 'Types', 'Edges', true); moi.selection.setFilter( 'Types', 'Points', true); moi.selection.setFilter( 'Types', 'Curves', true);}

---

i haven't thought that fillet can fail on curves
red - points selection to fillet -> if number is bigger then 1.66 fails to fillet, radius should allow that (no points nearby)

Image Attachments:
Screenshot_122.png 

---

found smt today and it's awesome ! Copy paste between Moi & Rhino ! Great one & thanks !

---

Hi Cemortan_Tudor,

re:
> i haven't thought that fillet can fail on curves
> red - points selection to fillet -> if number is bigger then 1.66 fails to fillet, radius should allow that (no points nearby)

Can you please post the .3dm file with your curve in it?

Thanks,
- Michael

---

error

Attachments:
fail1.3dm

---

O hayo !
several questions for today !
1. Are any other waiting events then pointpicker ? If so how do I write them ? ( ex: I wanna do a script that runs from 2 hotkeys, c +q, c +w or c +r)
2. I've read changelog of v4, there's a future that can store history from file to file, i thought i might be handy for storing history of fillets/chamfers or other global variables -> Notes, how do i write, get from notes, examples please
3. another script that can be handy will be to give smallest fillet possible, detecting smallest edge - there's a script for that, but connected to the selected edges list how do i get them !
4. get point position other then moi.ui.alert

---

Hi Cemortan_Tudor, thanks for posting the curve fillet file. I have a fix for that for the next v4 beta.

> 1. Are any other waiting events then pointpicker ? If so how do I write them ? ( ex: I
> wanna do a script that runs from 2 hotkeys, c +q, c +w or c +r)

There are other waitable objects than the pointpicker, including PointStreamPicker, ObjectPicker, OrientationEditor, CommandUIContainer, and PopupWindow which is the base class for flyout menus and dialogs. You can make an event loop calling waitForEvent() on any of those.

But for making a script that runs from 2 separate keypresses in sequence probably the way I'd try that is to open a dialog box on the first keystroke. Then when a dialog box has focus it can intercept all keystrokes and handle them with its own script code including overriding any normal shortcut key handling for the keyboard event.

You do that by implementing script functions for OnKeyDownEvent( event ) and/or OnKeyUpEvent ( event ) in a <script> block inside the dialog box .htm file. There's an example and comments in ShortcutKeyDialog.htm , that's the dialog that pops up when you add a new shortcut key.


> 2. I've read changelog of v4, there's a future that can store history from file to file, i thought i
> might be handy for storing history of fillets/chamfers or other global variables -> Notes, how do
> i write, get from notes, examples please

Well the notes is supposed to be used for storing some text information that can be displayed to the user just for additional information about the file. You can access it by moi.geometryDatabase.notes . It is stored in the .3dm file.


> 3. another script that can be handy will be to give smallest fillet possible, detecting
> smallest edge - there's a script for that, but connected to the selected edges list
> how do i get them !

Do you mean the largest possible fillet? There are many factors that would go into that beyond just edge length. For example fillets are wider or shorter depending on the angle that 2 surfaces are meeting at (see http://moi3d.com/forum/index.php?webtag=MOI&msg=9815.7 for an example) , it's not just edge length that determines the maximum size.


> 4. get point position other then moi.ui.alert

You mean you want to display x,y,z coordinates somewhere on the main window instead of in an alert dialog? Where do you want to show them?

- Michael

---

I know that's not vanilla, that's why i'm adding comments where I'm adding script for vanilla, later on other installations will be welcome to dl this scripts/modify
I'd wish to have a hardOps hotkey helper - xD far from that

added hotkey for closing curve/polyline while drawing
'c' - close curve

Attachments:
DoCurve.js

---

reworked offset curves
added hotkeys
r - realtime or throught pt
d - distance
s - sharp/round
t - trim
c - cap ends
b - both sides

wanna add one more future, dont know how to do it !
if on brep first point was on surface - restrict to normal, there's restrictToObject (dont know much about it) and havent found normal* as reference scripting

Attachments:
Offset.js

---

Show messages:  1-4  …  25-44  45-64  65-84  85-104  105-124  125-144  145-164  …  365-372