Hi Metin,

> Actually, the single most important viewport hack I'd love to see in MoI.ini or the
> preferences is being able to use Alt + RMB to pan at all times, particularly in the
> perspective viewport.

That should be doable.


> A second or alternative option I'd very much welcome is being able to use MMB for
> panning in all viewports.

This part confuses me though because MMB does already do panning in all viewports.

You don't need to set any option for it, that's the regular default behavior already.

- Michael

Hi Michael,

i was wondering about that: I know that you are still working on the text display for the snappoints (this little texts like Tang. Quad. Center...) for V4.
Do you think this new feature could get a user interface? At the moment you can only use the text factory to insert text into the drawing....
Just thinking...

Hi Ralf, yes I do expect to work on some type of "annotation text" as part of the work on dimensions as well.

- Michael

Hooray! Dimensions and text too.
eric

Wow you are the best!

Hi Michael,

Many thanks in advance for the Alt + RMB option for panning in all viewports.

Regarding panning using MMB: my mistake, sorry, I hadn't updated my Wacom settings yet for the latest beta, and forgot for a moment that MMB already pans the viewports.

A minor remark: after setting MMB to one of my Wacom pen buttons for the MoI beta, I noticed that you need to left-click to activate a viewport before MMB pans it. This is not the case when using RMB (assigned to an other Wacom pen side button). You can use RMB to pan an orthographic viewport or orbit the perspective viewport by simply hovering over it and using RMB.

Hi Metin,

re:
> A minor remark: after setting MMB to one of my Wacom pen buttons for the MoI beta, I noticed
> that you need to left-click to activate a viewport before MMB pans it. This is not the case when
> using RMB (assigned to an other Wacom pen side button). You can use RMB to pan an orthographic
> viewport or orbit the perspective viewport by simply hovering over it and using RMB.

I can't repeat this over here - here the MMB behaves the same as RMB and no additional left click is required.

Is it possibly only something that happens when you use the Wacom instead of a regular mouse? Or only in certain situations like the first time you switch to MoI from another app?

- Michael

Hi Michael.

Still error.
Windows 7.

Vladimir.

Hi Michael,

I've tried it again, and I consistently have to left-click (tap on tablet with pen tip) before I can pan a viewport with MMB (assigned to one of my Wacom pen side-buttons). This might be a Wacom pen only issue, I can't test that because I only work with the Wacom tablet for navigation, and I've got no mouse anymore.

You'd think though that if a pen-assigned RMB does work for panning as soon as you hover over a viewport, a similarly pen-assigned MMB should (be able to) behave the same way.

Hi Metin, do you have the most recent drivers from Wacom installed?

- Michael

Hi Vladimir, thanks for reporting that shutdown bug. It looks like MoI v3 also has a similar bug with that same sequence. I've got a fix for the next beta release.

- Michael

Hello Michael!

How are you ? I hope fine.

I SHALL START BY SAYING THAT I DON'T KNOW IF I'M DOING SOMETHING WRONG...but I think that now we have a serious problem with this V4.

I explain.

As you said some times ago, in order to get commands/scripts execution faster than V3, now all the code is executed into the MAIN thread.

And this is OK.

But now I'm experiencing a very serious problem.

When, for example, I try to perform a Fillet or any other command that for some reason takes long time and never ends,
I get Moi frozen and I can't do anything to CANCEL the command!
All I can do is to close Moi with task manager.

And if I didn't save my work before I run the command, all my work is lost!!

The problem is that I can't know if a certain command will run into a indefinitely loop, before I execute that command (for example fillet).

Please, add a mechanism that keep the fast command/script execution while prevent this situation.

I stay tuned.

Thanks.

Hi Marco, Fillets and other commands that might have a long execution time have a special asynchronous factory where the work for them is still done in a separate process called moi_commandprocessor.exe . When a command like that is running, it should still be cancelable, the work for the fillet calculation itself is not happening on the main thread even in v4, only the script logic is running on the main thread in v4. The difference from v3 is that in v3 both the script code and async factories were running in a 2 different instances of moi_commandprocessor.exe , in v4 it's only the async factories that are doing that.

I just tested over here and I can't reproduce an uncancelable fillet, I'd need to get an example file that demonstrates the problem in order to find out any more about what's going on.

- Michael

@You : "...When a command like that is running, it should still be cancelable,...
I just tested over here and I can't reproduce an uncancelable fillet, I'd need to get an example file that demonstrates the problem in order to find out any more about what's going on..."


Hmm....this is strange...
I can confirm that more than a couple of times I found myself into the problem I described...

Ok. ASAP I try to recover one of those files where I had the issue and I will let you know.

Stay tuned.

Thanks.

Hi Michael,

Yes, latest Wacom tablet drivers are installed. Wacom tablet type is Wacom Intuos Pro Medium size.

Hi Metin, do you know the specific model number of your Wacom?

I see for the Wacom Intuos Pro that there's a new model number PTH660 that's out and the older model number is PTH651 . I'd like to try and get the exact same model you have so I can test it over here.

Thanks, - Michael

Hi Marco,

> Hmm....this is strange...
> I can confirm that more than a couple of times I found myself into the problem I described...

That's definitely not the expected behavior, you may experience a short hiccup while objects are transferred over into moi_commandprocessor.exe but nothing at all like the long freezing you are describing.

Since it's not the usual behavior I will definitely need to get an example file where it's happening so I can examine it over here.

- Michael

My computer at work was behaving sluggishly today. Nothing to do with MoI, maybe with slow telephone wire internet.
The repair man tells me that the "wires down the street were poorly spliced," so I got a new wire...---Old infrastructure.

Is there a recommended software to run on a Windows computer to "tune it up," or find out why it performs poorly?

- Brian

Even my xfinity fast cable internet service at home decided to quit working for brief periods over xmas.
Maybe too many people playing games?

Hi Brian,

re:
> Is there a recommended software to run on a Windows computer to "tune it up," or
> find out why it performs poorly?

I'm not aware of any single fool-proof one myself. Probably the standard thing would be to look for spyware/adware, try ADWCleaner, Spybot Search & Destroy, SUPERAntiSpyware, Malwarebytes Anti-Malware, and HijackThis. Be careful where you get these from.

You can also run msconfig.exe and see what is starting up automatically, if you've got a whole ton of stuff on there uninstall or disable things you don't actually use.

Sometimes Anti-Virus software can hook into so many things it can greatly degrade system performance so you can try disabling that.

Also run Task Manager and click on the CPU column under the Processes tab and watch that for a minute and see if there is something that is chewing up a lot of CPU.

- Michael

Ok Michael.

I understand that you need a 3dm file to test.

But unfortunately today I'm very busy at work and I didn't find a bunch of minutes to find the 3dm file that caused the issue...

I will try my best to find it and send to you.

If I remember correctly when I had the issue I was performing a Fillet command on a messy geometry.
I was doing nothing serious, only a quick and dirt 3D doodle while I was waiting the compiling of my AndroidStudio projects.

So maybe I've discarded the model after the crash.

I will try to reconstruct what I was doing to replicate the issue.

I will let you know.

Have a nice day.