ciko's Recent Forum Activity

  • Safe area expressions don't work for me either...

  • It seems that SafeAreaInsetLeft/Top/Right/Bottom functions could solve those problems but they don't work, they show 0 in every situation...

    And don't now why those functions work in Cordova app (for Android with cordova-plugin-android-notch), but don't work in Construct which uses Cordova?!

  • Thanks, I tried again following your link by config.json and config.xml modification and it's works...

    LaurenceBedford

  • After 2 mounts you should provide at least explanation or suggestion for this, why those PlatformInfo functions don't work for notch/cutout area. This is must have features for any mobile game...

    Ashley

    Or we have to buy plugin like this constructcollection.com/construct-mobile-notch

  • After some testing I realize that PlatformInfo functions show values that don't depend of Notch (Cutout) area. Here is one example:

    1. On browser:

    - ScreenHeight-768

    - WindowOuterHeight-656

    - WindowInnerHeight-576

    - CanvasCssHeight-576

    - CanvasDeviceHeight-576

    - SafeAreaInsetTop-0

    2. On mobile (Scale outer, Portrait orientation...):

    - ScreenHeight-780

    - WindowOuterHeight-780

    - WindowInnerHeight-780

    - CanvasCssHeight-780

    - CanvasDeviceHeight-2340

    - SafeAreaInsetTop-0

    Ashley Should we use hide status bar until this gets fixed?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I have tried but it doesn't work.

    My project: Layout and Window (Viewport) size - 800 x 1280 (10:16 ratio), I use Scale outer, Portrait orientation and viewportfit is auto.

    If I try game on phone with same or bigger ratio, 10:16 or 3:2, PlatformInfo.SafeAreaInsetTop is always 0 which means that calculates Y axis, not unsafe/notch area.

    But if I try game on phone with smaller ratio like 5:3 or 21:9 PlatformInfo.SafeAreaInsetTop goes negative.

    So for my phone which is 19.5:9 ratio, it doesn't calculate Cutout/Notch area at all, its value is always -227 and doesn't depend of unsafe/notch area.

    Did I miss something?

  • I have similar problem. Can't detect notch (cut out) area on android phones. If I don't choose "hide status bar" in C3 build, notch area will not be visible anyway, but if I choose "hide status bar" and activate/deactivate notch on my phone all sprites will stay on same place, windowHeight and viewporttop doesn't help at all.

    Any suggestions?

    And also if it's only solution to build game with status bar, does windowHeight or viewportbottom calculate status bar or not?

    Ashley

  • Please, does anyone know how to add more fonts, for example Cyrillic one?

  • With this simple steps you can use Google Analytics without needing touse Firebase, it works for me...

    https://stackoverflow.com/questions/45853012/add-google-analytics-to-android-app-without-firebase

ciko's avatar

ciko

Member since 28 Apr, 2016

None one is following ciko yet!

Trophy Case

  • 8-Year Club
  • Regular Visitor Visited Construct.net 7 days in a row
  • RTFM Read the fabulous manual
  • Email Verified

Progress

11/44
How to earn trophies