Full Version: V4 beta Dec-12-2017 available now

Show messages:  1-11  12-31  32-51  52-71  72-91  …  172-176

Hi Ralf,

re:
> this is not working: Box3pts WidthHeight width=2 height=4

It looks like here you are trying to use the new variation of the box 3pt command that I posted yesterday?

The problem here is that the command name for that is Box3ptsWidthHeight, without any spaces in it, you've got a space in the middle of yours above.

- Michael

---

Hi Pilou,

> @Michael (just a little very cosmetic error from my part) (3 times in French "objects" must be "objets" tiny isn't it! : escaped till now! :)

Thanks, I've updated this for the next beta.

- Michael

---

Hi Shane,

> Hey Michael, I am having some problems with shortcut keys on the Mac. Fist there are
> duplicate entries for things like undo (Cmd+Z on the Mac) it also has a Windows entry of Alt+Z.
> I can't seem to set any shortcuts using Cmd+. I sometimes get a crash when attempting to
> set shortcuts. Crash report attached.

Yes, there's still a problem with Alt+ and Cmd+ getting confused with each other. I'll be looking at that for the next beta and I'll be checking out the crash today, thanks.

- Michael

---

re: options dialog crashing on close on Mac, looks like one of the changes for fixing the "mouse moves get ignored in some conditions" are causing that. I'll roll out an updated version soon.

- Michael

---

Seems a Mac a very sensible machine ? ;)

---

Hi Pilou, well this latest crash is from a mistake I made, it happens to be in an area of mouse event handling that is by its nature kind of sensitive.

There are some things that I have found frustrating with the Mac though, like the full screen mode and the "spaces" mechanism is very poorly documented and hard to control.

But I expect things to be reaching a good level of stability soon here.

- Michael

---

Hi Finema & Ralf & shane - re crash on closing options dialog on Mac, I just updated this to a new Dec-12 version which should hopefully fix that, please let me know if you still see it.

Thanks, - Michael

---

Hi Michael,
Thanks for the update, it's OK now.

---

That's great Finema, thanks for testing it! There are still some things to fix but hopefully we should be at a pretty stable version now.

- Michael

---

Does it necessary to reload the PC version ?

---

<<<<<The problem here is that the command name for that is Box3ptsWidthHeight, without any spaces in it, you've got a space in the middle of yours above

Yes but i tried different versions with or without space...

Looks like its not implemented right now..

---

Hello Michael,
for me on Win10, F10 Shortcut is not working, in previous beta this was OK.

- Scarab

Image Attachments:
F10_error.png 

---

Hi Pilou,

> Does it necessary to reload the PC version ?

No there's no changes for the Windows version.

- Michael

---

Hi Ralf,

> Yes but i tried different versions with or without space...
>
> Looks like its not implemented right now..

Did you install the plug-in into MoI's commands folder?

- Michael

---

Hi scarab,

> Hello Michael,
> for me on Win10, F10 Shortcut is not working, in previous beta this was OK.

It looks like you've got the FullScreen plug-in installed in the previous beta but not installed in the new one, you'll need to copy it over into the new beta's commands folder to make the new beta able to locate it.

- Michael

---

Hello Michael.

@You "...There are still some things to fix but hopefully we should be at a pretty stable version now..."

Wow! That's great!

Does it mean that soon you will able to start coding new features for this V4 ?

:)

Have a nice day.

---

Aaaaah now i understand....

I was thinking its some new implementation which accesses the old commands...

---

Hi Marco,

> Does it mean that soon you will able to start coding new features for this V4 ?

Not quite yet, but that's getting close! There is still some work left to fix some remaining bugs and still a couple of display features to implement to reach full parity with v3. But getting rid of the bugs that most interfered with normal operation is a pretty big milestone, it seems like that's where things are right now.

- Michael

---

@You : "...is a pretty big milestone, it seems like that's where things are right now..."

Wanderful!!!!

Thanks a lot Michael.

P.s. please don't forget to resume the display of "snap" labels :)

Ciao!

---

Hi Ralf,

> I was thinking its some new implementation which accesses the old commands...

Well, there is indeed some new stuff that can be used with old commands for setting default values used by controls in the command, that's what those example shortcuts for Trim and Extrude are doing.

But that particular one you were trying was a customized command that altered the box3pts workflow a little bit for what Andreas was wanting to do. So for that to work at the moment you'd need to install the custom command.

It probably does make sense to incorporate an option for that behavior within the regular box commands too though, but that's not how the box commands are currently set up, because they don't currently try to look at any default values for width and height. They're expecting the width and height inputs to be changed just by moving the mouse around. They only grab width and height values from the controls if you type stuff directly in them.

Maybe I can tweak the new mechanism a little bit though - like if the control is marked as being non-persistent like the box width/height are, it should fire a UIEvent for that control (which will then trigger the script to get the values from them) rather than only setting the default. Maybe if I set that up then it would work with the regular existing box commands too.

- Michael

---

Show messages:  1-11  12-31  32-51  52-71  72-91  …  172-176