Just for info an update of the build 249 has been released in the MMF2 forum.
Printable View
Just for info an update of the build 249 has been released in the MMF2 forum.
Thank you, this is great work!
First remark: the Date & time object works excellent on Mac! The only thing is that it works in 12 hours format if it is set to 24 hours format.
Please look my problem with MobileFont in this tread :
http://www.clickteam.com/epicenter/ubbthreads.php?ubb=showflat&Number=161853#Post1618 53
I already mentioned this before.. ;)
My second remark: the Load Frame action of the Active object does not work. If the action itself is present in the built application (I mean: it doesn't have to be called by an event), the application crashes.
Fourth: The Active System Box works well in the Sub-Application!
Load frame action corrected. A stupid mistake.
Hmm, two separate threads about beta 6, but maybe I report on java mobile features here..
So unfortunately I have to inform you that, based on my first tests, XMouse and YMouse expressions are causing still a lot of crashes on mobile (touch devices) and do not work as they would need to.
What works now is
CASE A:
Always
- Set X position to XMouse
- Set Y position to YMouse
So this is fine, unlike to previous build.
But then if we have e.g. something like:
CASE B:
X(active) < X Mouse --> Set x position to X(active)+1
X(active > XMouse --> Set x position to X(active)-1
Y(active) < YMouse --> Set y position to Y(active)+1
Y(active) > YMouse --> Set y position to Y(active)-1
The object moves only on Y-axis on mobile and stays still on X-axis. When run inside MMF, it moves correctly.
CASE C:
However, if I have CASE A in frame 1 and then an event "press button --> jump to frame 2 (CASE B)", the app crashes with the following error message.
Class Cat
java.lang-ClassCastException
Expressions.EXP_XMOUSE
incompatible with Expressions
CExp0i
CASE D:
Also, if I have in third frame the new mobile font object with a string object and one event where I set the mobile font color to red, even the first frame (CASE A) does not start and the app crashes immediately when started with the message below.
Null Pointer
java.lang.NullPointerException
Additional remarks:
In general, a bit more complex actions involving XMouse and YMouse (in alterable values), like Sqr((((XMouse-X( "Active" ))*(XMouse-X( "Active" )))+((YMouse-Y( "Active" ))*(YMouse-Y( "Active" ))))) seem to crash.
Finally, when the screen is rotated, in CASE A the object doesn't follow the pointer (touch) correctly anymore, as it seems like the coordinates are not "turned around" like the screen is.
So a bit of a negative test result, but I hope it helps in validating and fixing these issues. I will provide more results when I have something new to report.
The mobile font problem has been corrected.
All the problems with XMouse came from a nasty bug that I found and corrected. The bug occured when you had on the same event program xmouse/ymouse and xactive/yactive.
It must have been present in the previous version I think.
Thanks for the report.
The problem with MIDI playback still exists - a MIDI will play multiple times, creating a loud echoing effect. Tested on MMF2 Standard Build 249 Beta 6 with Java version 1.6.0_15-b03
Steps to reproduce:
1) Make any event you wish (for example, "Start of frame") that will Play Music (with any MIDI you desire)
2) Build Java Standalone Applet
3) Run applet, shield ears
Here's a sample .MFA and compiled .JAR applet demonstrating this.
The music problem does not occur on my machine. I think it must be a problem on your machine, as I DO stop a previous music before starting a new one.
Can you try testing on another machine? I tested this on ten different computers and they all suffered the same problem.Quote:
Originally Posted by Francois
OK, I understand the problem now.
I have set breakpoints in the code, the music is only started ONCE and ONCE only. The code to start the music is very simple, there cannot be any error there.
The sequencer can only play one music at a time, it is not multitask.
It is very strange, the echo effect appears slowly. I think it is more of a problem in the MIDI routines of Java.
I think I cannot do anything against this.
OK I have tried with other musics from the MMF2 CD2. It works fine. No echo. This problem must come from your MIDI files.
Just to inform you that the bugs (case a-d) I reported in this post http://www.clickteam.com/epicenter/ubbthreads.php?ubb=showflat&Number=161976#Post1619 76 are fixed in beta #7.