A little request:

Right now the MacOS MoI V4 beta doesn't allow keyboard shortcut columns to be resized in the Preferences. This results in unreadable entries like this:



In this case it's not visible which Numpad keys are assigned to the Boolean functions. As I use the keyboard shortcut list often as a reminder which keyboard shortcuts I've assigned to functions, I'd like to be able to resize the columns if that's not a hassle.

In case it's not difficult, I'd also welcome an alphabetical sort option when clicking on a column header.

I'll also post this in the V4 wishlist discussion.

Thanks in advance.

Hi Michael,

I don't know if this has already been mentioned, but I noticed a bit of lag when dragging a selection range to select curve points in Show Points mode. The lag isn't there in the WINE V3.

— Edit: I also just noticed the lag when panning the viewport, with several curves and selected points visible.

I also noticed that when you drag across the radius input value field of a selected curve, if you touch the "Radius" text, it will change to Diameter while you're still dragging to select the value.

My system specs:

• iMac (27-inch, Late 2013)
• MacOS High Sierra, version 10.13.1
• Processor: 3.5 GHz Intel Core i7
• Memory: 16 GB 1600 MHz DDR3
• Graphics: NVIDIA GeForce GTX 780M 4 GB
• Wacom Intuos Pro tablet + pen, latest drivers

If MICHAEL builds a nice interface in MoI v4 for plugins (installing, search for new, update...)

MAX could sell his unbelievible and usefull Scripts for a fee...

And WE have the fun :-)

Hi Pilou.

For Windows7,
ProgramFiles/MoI4.0betaNov-18-2007/ui/nodeeditor/core/css/editor.css

MoI4...2007/ui/nodeeditor/core/editor.js

("same" as for MoI3 IMHO)

- Brian

@Bem : Thx ! That was not clear for me! :)
some files from November must to be remplaced the october ones! (2)
nodeeditor.css in C:\Program Files\MoI 4.0 beta Nov-18-2017\ui\nodeeditor\core\css\nodeeditor.css
nodeeditor.js in C:\Program Files\MoI 4.0 beta Nov-18-2017\ui\nodeeditor\core\nodeeditor.js

Now all is clear! :)

At first glance nothing to translate for general use! :)
For old nodes of course!

Does all the nodes of the // Elephant (Mkdm, Karsten, Al2000..) will work on this new version or they must be adapted too ?

CycloidGear11_to_1, and motor2017 run very well.

Hello Max.

This is a detailed report of the testing I've made so far on some of your scripts :
(please check the "FAIL TESTING" section)

****************************
SUCCESSFUL TESTING :
****************************

SCRIPTS UPDATED ON NOVEMBER 2017 :

OK : NutsAndBolts.v.0.96.2015.06.22.zip (Sun Nov 19 00:15:05 2017)
OK : FatLines.v.0.6.2017.11.17.zip (Fri Nov 17 00:13:10 2017)
OK : sSplit.v.0.95.2015.08.10.zip (Thu Nov 16 23:44:37 2017)
OK : sBridge.v.0.71.2015.03.26.zip (Thu Nov 16 23:25:04 2017)
OK : Gear.v.1.0.2014.09.26.zip (Thu Nov 16 22:51:13 2017)

SUBDIV SCRIPTS :

Ok : SubdivBeta.v.6.1.2015.03.05.zip (Sat Aug 29 15:55:16 2015)
Ok : SubdivBeta.v.6.1.2015.03.05.zip (Sat Aug 29 15:55:16 2015)

OTHER OLDER SCRIPTS :

OK : RandomCurves.v.1.0.2014.01.25.zip (Tue Nov 4 21:25:12 2014)
OK : PatternSelection.v.0.3.2014.02.20.zip (Tue Nov 4 21:16:34 2014)
OK : DistortCurves.v.1.0.2014.11.04.zip (Tue Nov 4 01:23:30 2014)

****************************
FAIL TESTING :
****************************

ERROR : Cloth.v.0.96.2014.02.23.zip (Mon Nov 3 23:56:24 2014)



Watch this brief video : http://take.ms/peCkR

ERROR : cMorph.v.1.1.2014.01.19.zip (Mon Nov 3 23:46:56 2014)



Watch this brief video : http://take.ms/RT7K2


We'll catch up.

Ciao!

Hello Michael.

During my random testing session of V4 I noticed that this shorctut key isn't fired up :

Ctrl+Shift+1 (I use it for show-hide edges on selected objects)

Also, if I try to edit this shortcut key and try to reassign it to the "Ctrl+Shift+1" combination,
when I hit the Ctrl+Shift and then the "1" key, I get "Ctrl+Shift+!" because I have an Italian keyboard :



Please check this brief video : http://take.ms/0xhsc

With the V3 I have the same keyboard shortcuts but all works fine.

Please, let me know what I have to do.

P.S. As mentioned also by another user (I don't remember who), please give us the chance to resize the first column of the shortcut key editor.

Thanks.

I stay tuned.

Ciao!

_nutsandbolts not works for me! (Windows 10)

Hi Metin,

re:
> A little request:
>
> Right now the MacOS MoI V4 beta doesn't allow keyboard shortcut columns to be resized in
> the Preferences. This results in unreadable entries like this:

Thanks for reporting this. I've updated this so the Key column should automatically expand if needed, so the full key text should always be visible now. You can update this in the current beta by copying the attached updated ShortcutKeysOptions.htm into MoI's UI folder.

Please let me know if you still have any unreadable entries.

re: sorting shortcut keys I'm sorry but I don't expect to be able to have that anytime soon.

- Michael

Hi Metin,

> I don't know if this has already been mentioned, but I noticed a bit of lag when dragging a selection
> range to select curve points in Show Points mode. The lag isn't there in the WINE V3.
>
> — Edit: I also just noticed the lag when panning the viewport, with several curves and selected points visible.

re: lag

Do you notice this lag with a completely empty scene with a maximized viewport? What number value do you see in the upper left corner of the viewport when you pan or rotate on an empty scene?

I wonder if your video card has to do extra work for the back buffer format that v4 is currently using.

- Michael

Hi Marco,

> Also, if I try to edit this shortcut key and try to reassign it to the "Ctrl+Shift+1" combination,
> when I hit the Ctrl+Shift and then the "1" key, I get "Ctrl+Shift+!" because I have an Italian keyboard :

I also get Ctrl+Shift+! for that key, but it's working fine if I use it. Does yours not work if you go to use it?

If I remember right this is a side effect from switching from Windows key definitions to cross-platform Qt key definitions, it reports things like !@#$ as being the keystroke when shift is being used. Probably shortcuts using those particular keys with shift modifiers will have to be redefined for v4.

- Michael

Hello Michael.

Thanks for the clarification.

@You : "...Probably shortcuts using those particular keys with shift modifiers will have to be redefined for v4...."

Ok. I remapped that key from "Ctr+Shift+1" to "Ctr+Shift+!" and now it works as excepted.

Thanks.

Please, keep in mind to allow as to resize the first column on the editor.

Have a nice day.

Many thanks for the keyboard shortcuts column resizing update Michael, much appreciated. It works fine.

I'll check the viewport refresh rate a.s.a.p.. My machine is currently heavily rendering, which will lag anything right now.

Some other things:

• If I enter a Command key shortcut, such as Cmd + E for export, then the next time I start MoI, the keyboard shortcut has changed to Alt + E, and neither Alt + E nor Command + E works.

• When the Obj export dialog is active, you can't navigate a viewport without exiting the export process. I use viewport navigation a lot when the export dialog is active, to zoom in on objects and check if the polygon detail is sufficient everywhere.

Hi Marco,

re:
> Please, keep in mind to allow as to resize the first column on the editor.

Please try the updated shortcut key editor from here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=8682.52

With that update, the first column should automatically expand to fit the widest shortcut key and so none will be cropped and there's no benefit to gain from also adding in column resizing.

- Michael

Hi Metin,

re:
> • If I enter a Command key shortcut, such as Cmd + E for export, then the next time I start
> MoI, the keyboard shortcut has changed to Alt + E, and neither Alt + E nor Command + E
> works.

This has to do with Wineskin using Alt as an alias for Cmd since Windows doesn't have a Cmd key. In MoI v3 you could use either Alt or Cmd for any of the Cmd shortcuts, they couldn't be set separately. I haven't quite figured out what to do about this yet.


> • When the Obj export dialog is active, you can't navigate a viewport without exiting
> the export process. I use viewport navigation a lot when the export dialog is active, to
> zoom in on objects and check if the polygon detail is sufficient everywhere.

I can't seem to reproduce this one over here, is there a particular method of view navigation that's not working? What happens when you click on the main window while the meshing options dialog is open, does it make a sound? By the way the weird little Mac classic wristwatch cursor will be gone for the next beta.

- Michael

Thanks Michael for the updated "ShortcutKeysOptions.htm".

It works.

But...we have another problem here, and this is more serious :)

As I told you in my previous message I remapped the "Ctrl+Shit+1" to "Ctrl+Shit+!" and all works fine until I only use V4.

But, when I close V4 and open V3, where I still have the "Ctrl+Shit+1" original shortcut, and then I reopen V4
the shortcut key is changed from the new "Ctrl+Shit+!" to the original "Ctrl+Shit+1".

But...V4 and V3 does share the same .ini file ? I hope not.

So, to recap, this is the step I did, if you want to make a test by yourself :

1) All Moi are closed
2) I open V4
3) I remap the "Ctrl+Shit+1" to "Ctrl+Shit+!"
4) I close V4
5) I reopen V4. All is as excepted. The new shortcut is there and it works.
6) I close V4
7) ************* I open V3 and check the shortcut keys : I have the original "Ctrl+Shit+1". OK, this is correct and it works.
8) I close V3 and open V4 again.
9) ************* Here's the issue. V4 lost the new shortcut "Ctrl+Shit+!" and instead have the V3 shortcut "Ctrl+Shit+1"
10) If I repeat the whole process I always get this issue.

I remember you that I'm running Windows 10 Pro 64Bit Eng.

Please check this issue when you can.

Thanks.

Hi Marco,

> But...V4 and V3 does share the same .ini file ? I hope not.

Yes they do, same as V1 and V2 shared the same .ini file, same with V2 and V3, and so same with V3 and V4.

But yes this is a problem that the shortcut keys for certain cases are interpreted differently. I'll either need to make those cases compatible or otherwise use a separate section in the file to save V4 shortcuts so V3 and V4 would be independent from one another in that particular area. Making them exactly compatible may be tricky to do in a cross platform way since it relied on some Windows functions.

- Michael

@You : "...Yes they do, same as V1 and V2 shared the same .ini file, same with V2 and V3, and so same with V3 and V4..."

Ok. I didn't know. Thanks for the info.

But the issue remains...

@You : "...otherwise use a separate section in the file to save V4 shortcuts so V3 and V4 would be independent from one another in that particular area. "

I think this could be a very easy way to solve this issue.

Thanks.