Hi Dokugogagoji,Dokugogagoji wrote:I was the builder but I haven't personally distribuited them and I am asking to remove those earlier builds from BadaItalia forum who started to do this with my nick. I have removed the link from the forum. I had a private Skydrive folder who have shared them with my friend... I have no doubt who distributed them. But he is not a developer, so no code change and the build was only binary.chrisws wrote:I wouldn’t trust the leaked version. The setup steps involve using a dummy certificate which could allow the app to do anything. There is no guarantee the code hasn’t been changed and no one is claiming to be the builder.
There were four builds where they were linked with the external libreries.
the first one missed the event manager, so it was unusable.
the second one leaked for every external libraries..so crashes for missing zlib imports and the flag USES_ZLIB makes it using comperssed saved game...and all FLAC/OGG/MAD support were missing.
the third one corrected the zlib issue.
the fourth one has libflac, libogg, libmad, libvorbis and game wip engines, fixes for Bada 2 (the volume slider is only visibile when running bada 1.0 and 1.2 ), removed control mouse only, long press for click, double press for right click.
md5 were the same from the multiupload leaked one so he has some arcane power to keep the md5 the same or probably it is not changed.
The modified code is all on form.cpp
certificate is the developer one, who it is used by Bada SDK. However, manifest.xml is not overrided by the certificate.
There is the SYSTEM_SERVICE privilege who
essential if your app is hungry for some system and runtime specific info like the memory or battery levels
With this privilege can't do anything else, so it can't use social and privacy sensitive api.
..however I have stopped to do them in the shared folder since I was wrong on trusting my friend...
Thanks for giving us the information about the leaked version.
Could you please tell me more about the "control mouse" change. Was this required for SDK 2.0? I think you will find the double press event interferes with some games such as "indy 4" and "full throttle" where you need to do a lot of rapid clicking to hit the game opponent. Also the "move only" option was there to allow the user to explore the screen for hidden objects without making the game character move.
I made many changes in this area after playing lots of games, but I guess there will still be better ways of handling this, so any feedback is welcome.