Important Bugs in iOS Export Module!

Hello Andos, and probe with Multitouch but not if I'm doing it the right way, I'm testing if the user touches the icon of the weapon and also occurs at the touch number 1 then performs the action. I do not work well, although I also believe that use the touch joystick "0" just should not be a problem, because when I'm not active arms touching the joystick. If you see something that I can suggest at the code level I thank you, I'm also thinking this has more to do with the video that plays two levels before and I'll explain here:

http://community.clickteam.com/showthread.php?t=69911&p=519724#post519724

http://img19.imageshack.us/img19/420...20403at184.jpg

Thanks for your help! :)

You should not directly use "touch number XX". This was a mistake of me to implement these conditions in the object. I'm going to leave the actions in the object, but remove them from the menu.
The problem is that, when you drop fingers on the screen, the touch number may not be the one you expect.
You should have an "On new touch" event, and get the "Last new touch" number. Then use it in the rest of the program. It has to be flexible and adapt to any situation. I am sure that your problems only come from that...

Well the truth Francois Multitouch is not my problem in my game, this was a suggestion to try Andos.

My real problem is simple in my game, I have a character who moves with joystick and seven Active Objects on the screen that represent their weapons. Most times I run the game on my IOS devices, if I touch any of the ActiveX Objects with my finger does not work, sometimes it works, is a random bug. I send the MFA both Andos like you, and that Andos found some bugs, like the monochromatic effect that applies transparency in IOS. Now I hope to see if we can resolve this bug is the largest of all.

Thank you very much!

The best way to isolate a possible bug is to try to reproduce the problem from scratch. Start a new app and insert only the objects and the events that are related to the problem. This makes it easier for everyone to spot possible bugs, or problems within your own code.

I still think you should reprogram you Touch events in the proper way, asking for the number of the touch from the object.

Thank you very much Francois, can you give me an example of how to do this. Anyway I'm sure this is not the problem but the IOS Video. Read what I wrote in the post of the new beta.

Multitouch :

- A new touch has occured
+ Set counter to last new touch number

Now use the counter as a reference for polling the touches.

Andos has corrected the video problem. we should publish a new version soon.

Thanks Francois for this example and good news! :)

These are the three most important bugs were not fixed in Beta 5, Andos work in the first two and the third is that Francois is aware, I love to see if there may be solutions to the Beta 6 (this is tested in the beta 5 of iOS Exporter)

Bug #1:

Quote:

---

Originally Posted by Koji_Kabuto

* Effect Mode: "Set ink effect to Monochrome " does not work properly. In iOS but does apply transparency effect (see flying robot in the iOS and PC screens).

http://img14.imageshack.us/img14/387...fecttomono.jpg

http://img804.imageshack.us/img804/8...fecttomono.png

---

Bug #2:

iOS Video if present in one of the frames before the frame of the game, disable mouse taps on the screen, it gave me a lot of headache to find it, is if the video ends (I guess this Andos work) and go to the next frame the problem disappears, but it is interrupted by a jump (a touch screen to continue), but send them to destroy the object before the output remains the bug. This I checked by removing and putting the MP4 file in Xcode project and the version without the video works perfect with the video goes described before.

Bug #3:

Already reported by some in the forum, if you use the same sample (same name) on another channel audio, no sound is played. This is extremely uncomfortable in a game since the tendency is to use the same sample for various situations such as the explosion of a missile.


I think these bugs are the most difficult to get and I guess to fix, but otherwise leaves the iOS Exporter almost 95% of perfection, it's fast, easy to program and with many additions in the future is not competent on the market.

Thanks Clickteam! :)

Francois, Andos,

Any comments on these issues?

Thanks for your response,