0 Favourites

Bring back usefull construct (fullscreen) !

  • Scirra/Ashley I beg you, and not only I but quite few developers I know, please bring back fullscreen workarounds that was available pre 147 version. If you are worried they are workarounds and work inconsistently maybe make it totally optional hidden and requiring some additional knowledge to activate.

    People that actually make games in construct2 really need these feature.

    Fullscreen API is not cutting it. Obviously with ios7 we can use minimal ui tag but game still needs to have fullscreen on ios6 and ALL android devices otherwise no one will buy them.

    With this single change you made entire construct2 useless for bulk of users that dont even bother writing here on forums because they feel powerless like they cant change your mind to bring it back.

    Improvements you are making to recent versions are great but what if tons of developers cant use it?

    Sincerely

    Professional Construct2 user.

    EDIT: Please dont use argument that pre r147 workaround was unstable because I heard not even single word of complaint from even single customer.

  • I agree with PKrawczynski for 100%. I really can't understand why it was dropped.

  • On top of that please look at one of threads when searching for construct 2 on html5game devs forum.

    html5gamedevs.com/topic/3351-hide-safari-address-bar-on-ios-6-in-construct-2

  • True. All sponsors request us to remove the address bar or they will not buy C2 games. I found a quote from Ashley about this issue on IOS:

    iOS 7 removed the ability to hide the address bar, and accordingly we removed the option from Construct 2 (the code is a horrible hack anyway which Apple appear to never have wanted to support in the first place).

    iOS 7.1 adds an official new option to show minimal UI, which we're already applying automatically in the latest build, so when that comes out it should be solved.

    The fact is that a lot of users still have IOS6. So even it is a horrible hack, at least keep it for IOS6. I know there are some workarounds but they are breaking fullscreen modes.

  • Hello

    I've been developing web(flash) and mobile games for 4 years now. Construct2 is a great tool and the lack of ios fullscreen mode is the only thing stopping me from buying a personal license. I belive restoring this feature will satisfy all construct2 users targeting web market. Also, a lot of publishers are waiting for html5 games working properly in fullscreen mode on ios devices.

    I'm hoping Ashley it will help selling more construct2 licences

    as there are probably more people like me out there.

    I was recommended to construct2 by PKrawczynski

  • It's true that sponsors won't accept games that doesn't support fullscreen. I really think Scirra team should look into this.

  • If that is really true, it should be corrected, mobile without fullscreen just does not cut it, I am against workarounds, but maybe keeping it and replace it when a better working solution is found.

  • As far as my own testing showed, the option never worked on Android, only iPhone. On Chrome for Android, the Fullscreen API is supported, which is a much better solution. You should start using this feature if you are not already ('Request Fullscreen' in the Browser object). Chrome is steadily replacing the stock browser on Android, and it's just a waiting game before it's the vast majority of Android devices. I don't know what more we could do for Android.

    iOS 7 removed the ability to hide the address bar, and the vast majority of iOS users are on the latest version - Apple are generally very good with getting everyone on to the latest version quickly. According to Apple's stats 82% of devices use iOS 7 and this number has increased about 3% in the past month, so soon enough it will be nearly universal, which to me would seem to make iOS 6 on the cusp of irrelevance if it is not already (notwithstanding fussy publishers).

    iOS 7.1 is due out in a month and supports the new minimal-ui directive. This is not as good as the fullscreen API in Chrome, but is a big improvement on iOS 7.0's restrictions. Soon enough after launch I would imagine the majority of iOS devices would be updated, and then the problem is solved for the majority, rather than a rapidly disappearing minority.

    If you have publishers who insist, and they cannot be persuaded otherwise, you can try implementing the scrolling hack using the Browser object's 'Execute javascript' action.

  • I am very keen to have full screen without bar.

    oops, will read ashleys response...

  • As far as my own testing showed, the option never worked on Android, only iPhone. On Chrome for Android, the Fullscreen API is supported, which is a much better solution. You should start using this feature if you are not already ('Request Fullscreen' in the Browser object). Chrome is steadily replacing the stock browser on Android, and it's just a waiting game before it's the vast majority of Android devices. I don't know what more we could do for Android.

    iOS 7 removed the ability to hide the address bar, and the vast majority of iOS users are on the latest version - Apple are generally very good with getting everyone on to the latest version quickly. According to Apple's stats 82% of devices use iOS 7 and this number has increased about 3% in the past month, so soon enough it will be nearly universal, which to me would seem to make iOS 6 on the cusp of irrelevance if it is not already (notwithstanding fussy publishers).

    iOS 7.1 is due out in a month and supports the new minimal-ui directive. This is not as good as the fullscreen API in Chrome, but is a big improvement on iOS 7.0's restrictions. Soon enough after launch I would imagine the majority of iOS devices would be updated, and then the problem is solved for the majority, rather than a rapidly disappearing minority.

    If you have publishers who insist, and they cannot be persuaded otherwise, you can try implementing the scrolling hack using the Browser object's 'Execute javascript' action.

    Can you then provide us with the code for it? Main reason why I use Construct2 is to not deal and learn JS. Just scrollTo(0,1) was all you were doing? Nothing else?

    Then I see totally no reason to remove it and just let it be since some people actually use construct2 to make games.

    I honestly have nothing more to say on this topic as all Im seeing is that whatever was in 146 worked perfectly for all clients and no one complained (except this funny minimal-ui on ios7).

    By now im exhausted with trying to explain to you reasoning of boostermedia, spilgames and other companies that actually matter in html5 world and are shaping landscape of games.

  • Actually let me add something here for clarity.

    If no one has working fullscreen on android - thats cool and okay, maybe android devs/browsers will fix it someday. Obviously you cant change browsers.

    I just see no reason to leave ios6 behind because you and only you see this as outdated os. Why am I forced to add this hack myself and why cant it be left somewhere in construct2 as legacy compatibility code. Why do I need even learn about this since that software was obviously made to spend least possible ammount of time on editing js myself.

    Sorry if I sound hostile, thats totally not my intention. English is just not first language and thats why I might have problems expressing myself in it.

  • Found chrome api:

    android chrome demo It works. Cool. Chrome full screen api

  • You don't need to use anything other than the 'Request fullscreen' action in the Browser object in Chrome for Android. One limitation is it only works in a user-input event, so you need to use it in an 'On touch' trigger or similar.

  • "you can try implementing the scrolling hack using the Browser object's 'Execute javascript' action."

    You mean you were just scrolling the page down, and so the iOS bar disseapeared? (like on some phone when you scroll the page down, the bar does not follow?)

  • Construct 3

    Buy Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Buy Now Construct 3 users don't see these ads
  • Hey Ashley, wouldn't it take you less time to share your script/a capx example than dealing with the same users requests ? I've seen it come back on the forums and twitter a couple of times now.

    I can attest that publishers have requirements that are set in stone, even if most of the user base isn't using ios6.

    Kind regards,

    Nathan

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)