Hi Michael,

it seems that openFileStream / writeLine / readLine functions are using Western codepage instead of UTF8. Mac version only.
I attached a nod-file with russian characters. Nodeeditor can't read this file properly.

Hi Max,

> it seems that openFileStream / writeLine / readLine functions are using Western codepage
> instead of UTF8. Mac version only.
> I attached a nod-file with russian characters. Nodeeditor can't read this file properly.

For the next beta I've converted the internals of openFileStream to use the Qt text stream functions, it should provide better consistency in unicode support like be able to detect any encoding signature at the start of the text file and use UTF-8 by default.

- Michael

Hi Michael,

Thank you! Could we expect a binary read/write functions in v4? ;)

Hi Max, I'm not sure about that, there could be some complications like trying to send binary data back and forth using strings can run into problems with things like illegal character encoding sequences and 0 values being treated as end of string markers.

There is a new kind of "typed array" thing that's meant for working with binary data in JavaScript but the version of JavaScriptCore that MoI v4 is currently using doesn't seem to have it included in the JSC API yet. That might not be possible without updating to the latest QtWebKit which is unfortunately a highly time consuming job.

- Michael

Hi Michael.

Paste does not work from the context menu of the mouse.
Video attached.

Vladimir.

Hi Vladimir,

> Paste does not work from the context menu of the mouse.
> Video attached.

Thanks for reporting it - I've put it on my list and I'll look into it next week. It won't be fixed yet for the very next coming beta since I want to release one soon, hopefully later today.

- Michael

Hi Marc & Metin,

re:
> On thing I noticed is the 'live' aspect of extrude seems slower in the Mac version than Windows.

I can see this here too, thanks for reporting it. I've got it on my list now and I'll look into it next week, it won't be fixed for the very next beta quite yet.

- Michael

New version of CMorph by Max Smirnov
http://moi.maxsm.net/media/files/
V4 (Windows 10)

New version of NutsandBolts by Max Smirnov
http://moi.maxsm.net/media/files/
V4 (Windows 10)

New Cloth for V4 by Max Smirnov
(V4 Windows 10) (was fine in the V3 with old version :)

Hi Michael,

In the hope that the following will assist in bug hunting:-)

Besides the non-working SpurGearProfile script, the LogSkelion script, which permits selection of a center point, does not work.

Today I tried out the JacobianFunctionGraph script, which uses color (style) selection.
It gives a weird error,
ReferenceError: Can't find variable: font
Line 16, there is a {
g_style_index = 0;
} there.
(I removed the "curly brackets" { }, and it seems the g_style_index = 0 is the problem line.)


Also, Please note that the script JacobianFunctionGraph-copy does not load the copy, it loads the original, JacobianFunctionGraph, with Max's customUI.
Maybe it is a customUI problem. Wen the modified script was renamed JacobianFunctionGraphMOD, it loaded properly.
(I have "DisableFileCaching = y in MoI.ini.)

- Brian

Just installed a Samsung 28", UHD 4K monitor, model UE510, 28."
The quality of the display is very nice.
- Brian

Hi Brian, re: JacobianFunctionGraph not working, it looks like when an exception occurs in script from the .htm file the display of the lines of code with the >>> marker in it is not accurate, so disregard that part of the error message in this case and only pay attention to the top that says "ReferenceError: Can't find variable: font".

I looked around and it seems that this function in _JacobianFunctionGraph.htm file is were the error is at, I've marked the use of setting properties on font but there does not seem to be any such object. Looks like font will be 'undefined' an you can't assign properties to 'undefined'. Maybe exceptions in .htm file code in V3 were silently ignored or something like that which is why it's different there:

		<script>
			function PopulateFonts( factory )
			{
				var FontList = factory.getFonts();
				
				for ( var i = 0; i < FontList.length; ++i )
				{
					var Option = document.createElement( 'option' );
					var FontName = FontList.item(i);
					Option.text = FontName;
					Option.value = FontName;
					
>>>>				font.add( Option, i );
				}
				
				var InitFont = 'Arial';
				try
				{
					var PrevFont = moi.command.getOption( 'Text.htmDefaultFont' );
					if ( PrevFont != '' )
						InitFont = PrevFont;
				}
				catch(e) { }
				
>>>>			font.value = InitFont;
				
				text.style.fontFamily = InitFont;
			}
			// Left out Initialize() and Shutdown() functions
		
		</script>		

- Michael

Hi Brian, so re: JacobianFunctionGraph - it kind of looks like the entire PopulateFonts is maybe pasted in from a different command and shouldn't be in there at all? It seems to be referring to controls that are not in the .htm file. It looks like you can just remove it and remove the 2 calls to it in the .js file and then JacobianFunctionGraph appears to be working.

I guess probably in v3 the exception generated in the .htm code is silently eaten, as if there was a try/catch around the whole function.

- Michael

Frenchy Pilou
>>New version of CMorph
Fixed

>>New version of NutsandBolts
Can't reproduce this error

>>New Cloth for V4
Lets wait for a new v4 beta

Hi Brian,

re:
> the LogSkelion script, which permits selection of a center point, does not work.

On _LogSkelion.htm line #186:

	<td><moi:UnsignedIntegerInput id="W" style="width:3em;" default="1.0" binding="Wslider.value = this.value"/></td>

Change the default="1.0" to default="1" and then it should work.

I've tuned this up for the next v4 beta which I think I might have ready tonight, so that default="1.0" on an integer input will work same as it did for v3.


re: SpurGearProfile - was that one of yours or one of Max's ? I looked on Max's file archive and only saw a _Gear one, is SpurGearProfile different?


- Michael

@Max
cMorph for V4 (Windows 10)
Perfect!
Just a little question!
(it's Curves and not PolyLines)



So maybe if you want grid:)

Thank you Michael,

Still digesting your posts :-)

The SpurGearProfile is a very old script, by someone else, maybe 2008?
http://kyticka.webzdarma.cz/3d/moi/#SpurGear
(So based upon your posts, my guess is that there is something else causing the error message, not just the first "variable/item...." in the script)

The JacobianFunctionGraph uses code from MoI's TEXT command/factory and in MoI3, displays some text.

-Brian

Hi Brian,

> The JacobianFunctionGraph uses code from MoI's TEXT command/factory and in MoI3, displays some text.

Right, but the problem is that some of that code from MoI's Text command is trying to access UI controls (like for the font dropdown) that were in the Text command but are not present in JacobianFunctionGraph. This is happening in the function PopulateFonts() in the .htm file. If you remove that function, and also remove the 2 places in the .js that were calling it, then I think you should avoid that 'font' error.

Basically the text command in its UI had a <moi:Select id="font"> which that code would add stuff to, JacobianFunctionGraph doesn't have that control in its UI yet it is still trying to run the code that added to it. In v3 it just happened that the error was silently masked.

Hope that makes sense! :) The other parts that use the text factory for generating text curves are fine, those ones are not trying to access any UI controls that are not present in this command. The one that's the problem is PopulateFonts() in the .htm file.

- Michael

Hello Michael.

As usual, I've a little "developer side" request :)

Just in order to keep us up to date about which are the "internal" changes of the new V4 betas,
could you please create a unified page or (better) a shared PDF file, in which we can easily find all the changes (small or big) that
you are currently doing or you already did to the Moi's Api/Css/Dialog/HTML/invocation method/numeric fields/UI changes/etc..., compared to the V3 ?

In this way all of use that want to correct old scripts or write new ones, can easily reach all the necessary information,
without having to dig into the "mare magnum" of all the posts here and there related to the V4 beta.

This could be a great, huge help for all of us that are engaged into the "coding" activity.

Thank you very much.

Marco (mkdm)