Posts by LostFoundry

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.

    I am really sorry to ask the same question, but how can the problem be fixed without an update to MMF?
    Is it OK for me to upgrade my developing environment to IOS5?

    I am using MMF build253

    I realise that scrolling has been discussed elsewhere... its just that I can't seem to solve this problem.
    I am trying to create a frame that infinitely scrolls in the X direction.

    Frame width is 10000, and I have set Virtual width to -1.
    The viewport is always centred on my space ship object

    From the forums, it seems that infinite scrolling can then be simulated by setting the X position of the spaceship to about 1000000 at the beginning of the frame, so as to give loads of left and right movement space.

    However, when I do this, the X pos of the active object sets itself to a negative number. This seems to happen when x>32000.

    Have things changed with updates to stop this from happening.
    Any advice would be greatly appreciated.

    Dear all.
    Just wanted to post the following app rejection reason, and the solution we implemented:

    Reasons for Rejection:
    10.1: Apps must comply with all terms and conditions explained in the Apple iPhone Human Interface Guidelines and the Apple iPad Human Interface Guidelines
    Aug 24, 2011 10:51 AM. From Apple.
    10.1

    We found that your app does not comply with the Apple iOS Human Interface Guidelines, as required by the App Store Review Guidelines.

    Specifically, we noticed your app only supported the top-up variant of the portrait orientation, but not the bottom-up variant.

    While supporting both variants of both orientations, each with unique launch images, provides the best user experience and is recommended, we understand there are certain applications that must run in the portrait orientation only. In this case, it would be appropriate to support both variants of that orientation in your application, e.g., Home button up and down.


    So even if you have selected one particular orientation for you MMF2 app, they could reject it as with the current options available on the iOS exporter, it will not work in the upside-down position.


    Or solution was to add the following lines to the file MainViewController.m (found in Classes->Application.)
    This was for an app that had to work in portrait mode.

    Add the code at the end of the file, just before the last line that reads "@end".


    - (BOOL)shouldAutorotateToInterfaceOrientation:(UIInterfaceOrientation)interfaceOrientation {
    // Rotate for portrait only
    return UIInterfaceOrientationIsPortrait(interfaceOrientation);
    }


    Perhaps this option needs to be implemented in the iOS exporter itself to avoid further rejections?
    What do you think?