WackyToaster's Recent Forum Activity

  • I´ve encountered this issue before and I could never find a clear answer to it. Worst part is that some phones handle it by zooming out while others don´t. Also I remember I found some settings to add (back when I was still building with cordova CLI) but this only worked for some phones and not for others because... reasons? Further, if you maintain a regular app and a webapp, you might find that the same phone handles webapp and regular app differently (one does the zoomout, one doesn´t). I also wouldn´t be surprised if there is differences between browsers too.

    I find it to be a pretty convoluted problem (and I think it shouldn´t have to be but what can you do...), and the best solution may actually be to implement your own keyboard and suppress the native keyboard if possible, which it may not be in all cases.

    EDIT: I just noticed that you use the preview, try building a debug apk and see how it behaves on the phone. It may work different when build as apk (or not... read above)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Sort of, yeah. I wouldn't even need/want individual pixels. I take triangles at ~10px too, probably even bigger.

  • Since we are talking about polygon decomposition... would this allow objects to break/shatter into smaller individual pieces from a big one? That would be cool :)

  • This is causing me to hesitate releasing the plugin. Depending on what you want out of the plugin, this could be a show-stopper...!

    You can always release it as a beta if you are unsure, as soon as more people use it it´s likely that they will find a bunch of bugs you never found anyway. Every software has some quirks or bugs here and there and often there are ways to live with them or work around.

  • The easiest would be to stagger the loading a bit like

    Load dictionary

    Wait

    Load dictionary

    Wait

    ....

    Go to layout

    The animation will still stutter a bit though but at least it won't look frozen. On that note, I've never seen a loading animation not stutter. The actual use of a loading animation is to let the user know that everything is still running (and not frozen/hanging)

  • You do not have permission to view this post

  • This is because mouse and touch behave a bit different overall.

    Mouse can get a position all the time, you don´t have to click.

    Touch can get a position BUT you can only get that position when you are actually touching. (How else would that work, there is no "mouse hover" equivalent)

    Holding click should work since you are simulating touch. If that isn´t what you want you´ll have to split those up as BadMario suggested.

    *grabs popcorn*

    I don't understand why you'd use this weird setup with return value. Why not just do

    FunctionA

    FunctionB

    FunctionC

    ...

    And maybe use signals/wait for signals if needed?

  • Hard to say without seeing the code in question.

  • I actually just unpack the c3p whenever I'm done for the day. Works fine too unless you like to commit every small change individually.

  • Hell yeah, forum drama!

    But I´d agree that the output looks confusing, lucky I never worked with 3D arrays before. I like mekonbekons idea.

  • I don´t think so. Also I think I mistook match rate with fill rate (unless they are the same... duh, I´m not 100% sure)

    Here´s some info about the fill rate with some possible explanation and things you could try.

    stackoverflow.com/questions/4895151/admob-really-bad-fillrate

WackyToaster's avatar

WackyToaster

Member since 18 Feb, 2014

Twitter
WackyToaster has 25 followers

Connect with WackyToaster

Blogs