SoldjahBoy's Forum Posts

  • R73 fixes this problem, but now introduces a new one.

    Scale mode no longer scales properly when making the window smaller... only when it is made larger. It's fine at any size when the layout first loads, but will not dynamically size itself should the user change the browser window size (smaller only).

    ~Sol

  • Ah, hadn't realised r73 was released. I have been busy with last minute Christmas cheer (tm) around the house. Will check it out ASAP and report back. :D

    ~Sol

  • Sure, just delete the iframe and the standard button still has the problem... see the posted capx in my second post, it only has a button with no extra plugins.

    ~Sol

  • Wow hard, no kidding. I got to stage 5 or 6 then died in 2 seconds.

    Some kind of leveling system would be awesome, so you can have better hit-points and resistance to things. Hard is good, but wowee the difficulty curve is like running head first into a brick wall D:

    It's very cool though, and reminds me of a more modern day Gauntlet :D

    I also agree that a slightly less "too many buttons" weapon system would be good, though keeping arrows as an additional or alternate fire style weapon is great.

    I look forward to seeing future updates to this ;D

    ~Sol

  • Cool concept :D

    Looks really nice too for such an early stage game!

    ~Sol

  • Pretty nice game :D

    I like the over-all presentation and the progressive difficulty. Very cool!

    ~Sol

  • Here is a capx with just the button... since it will be easier to look at I guess: dl.dropbox.com/u/604141/Public%20CAP/UpdatePositionBug-ButtonOnly.capx

    I put a text box in there for positioning reference.

    ~Sol

  • Artwork looks really cool. I'd like to see more :D

    ~Sol

  • You do not have permission to view this post

  • You do not have permission to view this post

  • CAPX: dl.dropbox.com/u/604141/Public%20CAP/UpdatePositionBug.capx

    It also uses JesseJoh's HTML Elements Pack: scirra.com/forum/plugin-jessejohs-html-elements-pack_topic47084.html

    The problem only exists when two conditions are met;

    • Fullscreen in browser is set to SCALE
    • Unbounded Scrolling is set to ENABLED/TRUE

    Only when these two options are enabled, the iFrame object specifically, seems to be bound to the coordinates of the browser window itself rather than the layout/canvas. Using any means to move the object results in additional problems, causing the object to move unpredictably around the browser window (or even outside of it!) while using the mouse to resize the browser window at runtime.

    Using events to "create iFrame at X,Y" will also result in the object not appearing in the correct position.

    The problem is more obvious on a layout that is portrait in orientation rather than a perfect aspect landscape layout.

    After talking with Kyat and Newt in chat... we have all deduced there is a problem here somewhere. Kyat suggests it may be in the code from your button object, as JesseJoh seems to have used that portion of code in the iframe positioning. Come to think of it, I believe the buttons also suffer this same problem so it could indeed be related.

    If you need any more info, let me know. Thanks Ashley :D

    *EDIT*

    Added a button to the layout as well, and yes... it's the same problem with the button as well!

    ~Sol

  • In future please be more specific with your requests. Not only will it help you get an answer faster, it saves on needless replies and further questions being asked.

    Other than that, glad you found what you needed... whatever that was.

    ~Sol

  • This is working fine in construct 2?

    Works perfectly, unless you use "stretch to fit" AND "unbounded scrolling" at the same time.

    At least, that's the only problem so far that I have found.

    ~Sol

  • Hate to sound like a rush, but... any news on finding this bug so far?

    ~Sol

  • Murkat, try to reverse your picking.

    If you are picking table vs. scientist, with the scientist as the condition... try making the table the condition instead. Get what I mean?

    That will probably fix your issue :)

    ~Sol