Full Version: V4 beta Feb-9-2018 available now

Show messages:  1-7  …  28-47  48-67  68-87  88-107  108-127  128-147  148-163

Hi,

New Mac Wacom drivers won’t resolve the middle clicking issue (6.3.28.2).

I was wondering if there was any way to revert to the old way of two finger scrolling to zoom?
It may sound counter intuitive but I always use the pen's the middle button to pan.
The pinching method doesn't work as well for me.

Also, is there any way that Moi exports to the last used folder (of the last session)?
I always export temp stuff to desktop.

Marc

---

Hi Michael,
I re-installed Moi4FebBeta, over its previous installation, and all is well.

The file GetPointOsnappedOnCurve.js was present, but I think the problem was that in between the recent customUI upgrades, I had modified CommandBar.htm, which is no longer necessary for "AppData..." storage... Sometimes its better to "let the dust settle." :-)

So at work all of the stock Commands are under ProgramFiles/MoI 4.0 beta Feb-9-2018/commands

_prefix commands are in another commands directory a few directory levels below AppData..., but could be in the old commands folder. (I think)


- Brian

---

Thanks Brian! That did the trick!

---

Hi Michael T,

re:
> I'm sure this has been covered before, but how (if) can I use my v3 .ini file and scripts with the v4 beta?

Your moi.ini file should be used automatically unless you have some custom setup for it.

For scripts, any commands you added to v3's commands folder will need to be copied into v4's commands folder. With this latest v4 beta instead of copying them into the commands folder in the install directory, you can instead copy them into the new AppData commands folder which on Windows is at C:\Users\<username>\AppData\Roaming\Moi\commands, on Mac it's /Users/<username>/Library/Application Support/Moi/commands .

If you copy them to the AppData commands folder you won't have to copy them again when new beta releases come out since that's a centralized location that can be shared between multiple installs.

- Michael

---

Hi Marc,

> New Mac Wacom drivers won’t resolve the middle clicking issue (6.3.28.2).

That's unfortunate. Hopefully with the next one. When I submitted the bug through their developer portal I got one notification right away that it was set to active status or something but I haven't heard anything else since then.


> I was wondering if there was any way to revert to the old way of two finger scrolling to zoom?
> It may sound counter intuitive but I always use the pen's the middle button to pan.
> The pinching method doesn't work as well for me.

There isn't currently any way to revert two finger scrolling back to mousewheel zoom but I can add a setting for it.


> Also, is there any way that Moi exports to the last used folder (of the last session)?
> I always export temp stuff to desktop.

There isn't any way to do this currently either but I can add in a setting for this too. Currently the default location will be whatever the operating system has set as the current working directory. On Windows there's a properties setting for shortcuts for setting the current directory for the program, it seems that there isn't an equivalent thing on Mac I guess.

- Michael

---

Hi Michael,

I've just installed the new Wacom drivers for Mac OS, and the issue where you had to left-click to activate a viewport seems to have been resolved. I can use the right mouse button to navigate in any viewport again by just hovering my pointer over a viewport.

---

That's great Metin - I wonder why it didn't work for Marc though.

- Michael

---

Thanks Michael, Brian straightened me out with the same advice.

Looking forward to running v4 through the paces!

Michael T.

---

Hi Michael,

Thanks, it would be nice to have those settings if it's not too much work.
Concerning the Wacom pen, it does work with right click, not middle click, kind of weird.

Marc

---

Thanks for all the great updates Michael - especially the curvature analysis script interface methods.

Some feedback:
Moving the the commands folder to %APPDATA%\Moi - is definitely a nice feature, but I wonder if the moi.ini file couldn't also contain one or more locations to search for external scripts? For some time I've been keeping all my scripts in Dropbox\MoI\commands, to enable the same scripts to be used from my (Mac) laptop via a Symbolic Link and (Win) PC via a Directory Junction. I appreciate I could easily make that Link and Junction 'just-one-last-time' now the new directory structure exists, but why not let a user specify one or more external script locations in the ini? It could also enable clearly separating beta scripts from full releases, or personal scripts from public ones, for example. Or is this what the %APPDATA%\Moi\startup folder can be used for?


And a question on script compatibility between v3 and v4:
I can't work out what change is required by the Script error thrown when I try running my NACA airfoil script in MoI v4.
"Required function argument 1 (object) missing."

Does MoI v4 require stricter adherance to Javascript best practices?
https://www.w3schools.com/js/js_best_practices.asp

Any suggestions appreciated, thanks.

---

Regarding the weights:
Is the weight information lost?
How is it connected, or associated with the points?
...
- Brian

Is the new chrome OK?

---

Hi Hamish,

> I wonder if the moi.ini file couldn't also contain one or more locations
> to search for external scripts?

I should be able to set that up.


> I can't work out what change is required by the Script error thrown when
> I try running my NACA airfoil script in MoI v4.
> "Required function argument 1 (object) missing."

I'm traveling for the next few days and I can't run the script at the moment. Can you post a screenshot of the full error dialog? That may give me enough information to help you now, it may be a few days before I can give a definitive answer though, it may be a function in MoI v4 that accidentally has a function argument set as required when it was optional in v3. Once I figure out which one it is I should be able to change it in v4 to be optional again.


> Does MoI v4 require stricter adherance to Javascript best practices?

Yes v4 is more sensitive to syntax errors that were tolerated in v3, but probably this one is a mistaken change in v4.

- Michael

---

Hi Brian,

re:
> Regarding the weights:
> Is the weight information lost?
> How is it connected, or associated with the points?

I think I may have missed the weights discussion that you are referencing, but the weight information is associated with the points by a fourth coordinate parameter on a control point like x,y,z,w values for each control point.

- Michael

---

Hi HAIRYKIWI :-)

I found the problems in the NACAAirfoil script:
At line 595 in the js you find this line:
"FactoryAirfoil.setInput( g, PointObjectListUpper.item(num_stations - g).pt.get );"
this ".get" seems to be not toleratet by V4
just delete the .get to "FactoryAirfoil.setInput( g, PointObjectListUpper.item(num_stations - g).pt"
repeat this to every line where you find this ".get" and it will work

Or just take the js in the attachment

Attachments:
NACAAirfoilGenerator.htm
NACAAirfoilGenerator.js

---

Hi Michael and Ralf,

Michael - many thanks for taking a look at the .ini option for specifying locations of external scripts.

Ralf, You're a star. Thank you :)
Modifying NACAAirfoilGenerator.js as you suggested cured the problem in MoI v4 - on both PC and MAC.
Out of interest, how did you debug it? Or did you find/remember some change of method to accessing ObjectList items in v4-compatible scripts?

I've become quite rusty with scripting since I wrote it and nothing really stood out in the script documentation http://moi3d.com/wiki/Scripting especially Max's mirror of Dave Morrill's script documentation/api/

It'll be interesting to hear from Michael if this change of access was intentional :)

---

Hi HAIRYKIWI,

First: WOW nice script very complex! THANK YOU

the trick was actually very easy...
I wrote this line into the script: moi.ui.alert("STOP");
Than running the script. If i got the "STOP" alert before the script fault message the fault must be hidden somewhere later in the routine..
doing this step by step further in the routine i could locate these bad lines... as a fortune my script editor (TextWrangler) already marked this ".get"s as a command - so just deletet them - that was all... I'm just a hobby scripter...

I think the incompatibility of some older scripts with V4 is that it uses a newer webkit which is more nitpicking...

---

Great debug tip Ralf - many thanks!

Now you mention it, I guess I did used a related debug method before - for printing variable values to the screen, but also being an infrequent hobby scripter, I frequently forget such elegant methods - and it never even occurred to me to adapt it, so again, many thanks :)

---

Thanks Ralf for figuring it out!

So if I remember correctly in MoI V3 and prior there was a pt.get() function set up but it was only callable from C++ code and not JavaScript code because it took 3 pointer values which JavaScript is not able to express. However just the presence of that method happened to have a side effect of pt.get not being a syntax error in v3 although it would not actually do anything useful.

In v4 the script interface is no longer based on IDL/IDispatch/COM Automation to be cross platform and the new interface only supports constructs that are compatible with JavaScript so the pt.get() method has been removed in v4.

- Michael

---

Hi Michael,

Much appreciate the explanation - even if I don't quite understand how I interpreted the documentation to arrive at my bad code in the first place :)

- Hamish

---

Thank you Michael.
I bought "The Nurbs Book."
Now I just have to read it...
- Brian

---

Show messages:  1-7  …  28-47  48-67  68-87  88-107  108-127  128-147  148-163