fongka2

Thanks for the example, but that does not necessarily solve my problem. My image assets are never the same dimensions, they will be dynamic so I can not give exact hard-coded math formula like you have for your objects as they are not dynamic.

A user will be uploading images on their own, so height and width dimensions will always vary.

Anyone know of a good way?

no one has experienced this?

Greetings...

I have been testing Crosswalk x86 APK's today, using the Google Android SDK with Emulator.

The ARM version of my app is fine, however when I try a Intel Atom x86 based APK on a x86 based emulator, I come to a weird (bug?) sort of thing...

When you touch a textbox DOM object, it will remove that textbox object and any remaining textbox objects on the canvas.... when I try to type something in, the text will not appear either, has anyone else experienced this issue?

The keyboard tooltip will sometimes show up if I spam touch where the textbox should be, so maybe its just dissapearing from the canvas but is physically still there?

This also might be for IntelRobert

Thanks

Hey everyone. Hope you are having a good day.

I have been trying to find a way to resize a sprite whenever I call loading an image from a URL. Been having a hard time grasping this concept for a good while.

I want to load the image into the sprite, resize it to fit a mobile phone screen size. I know how to resize to the screen, but it gets all skewed and the actual image dimensions get messed up and the image doesn't look right. So how could I approach resize the image based on its dimensions, but still be able to fit the screen size(mobile)?

I tried using the Sprite.ImageHeight and ImageWidth checks, I think I am on the right path, but not total for sure.

This would have been an easy fix by hard coding the right size, but the images will be dynamic via user uploads. So I have to think of a dynamic scaling system.

Thank you for your time!

Edit: I have gotten close to getting this working however this aspect ratio just does not meet my requirements.

Works!

I tested my app with the newest release (169) and it does not move canvas anymore!

Thanks, great news!

You're an extremely talented programmer, thanks again ASHLEY.

Even though the file size is quite large, it will not pick up a huge amount of extra size when you build upon your app. I have an app with over 400 events, and 600 sprites. My file size is approx 19mb.

Problem Description

When touching and holding down a textbox object inside Crosswalk, then swiping up while holding down, still... the canvas moves.

NOTE: It still moves canvas, slightly when you use this capx I provided, my main project moves canvas further, I am not sure what causing this, as they are both identical capx.

See my thread with some screenshots: https://www.scirra.com/forum/viewtopic.php?t=104121

Attach a Capx

https://drive.google.com/file/d/0B8m5DDRraPJoUmZkc2E2S0lRb0E/edit?usp=sharing

Description of Capx

Demonstrates that canvas moves while touching, holding and swiping up the textbox object.

Steps to Reproduce Bug

• Step 1: Touch and hold textbox object
• Step 2: Keep touching textbox
• Step 3: Swipe up while holding

Observed Result

Canvas wants to move, revealing black background underneath canvas.

Expected Result

It should not move canvas, it doesn't look professional when it moves.

Affected Browsers

• Chrome: YES (Crosswalk)
• FireFox: N/A

Operating System and Service Pack

N/A

Construct 2 Version ID

Latest Stable (168)

Aphrodite, I tried searching this issue before, it is kind of weird that no one else had caught this. It is unacceptable, because it (to me) frays the quality of the app .

Hello

I have ran into a snag using Crosswalk, whenever I use a textbox object in my app, and export it to Crosswalk, the app tends to scroll if I try touching the textbox and swipe my finger up, it makes my app all funky, it scrolls the ENTIRE canvas.

(it also does this in Chrome for Android as well, not limited to Crosswalk)

Here is the screenshots in action, the first screenshot is just the normal app before I touch the textbox object, the second screenshot shows the textbox object after I touched and swipe my finger up. Why does it do this?

Before swipe

After swipe

Ashley, maybe you know?

Thank you for the feedback.

Ashley, do you think there will ever be a chance where I can access the users phone and allow them to select a photo and upload it into a sprite, since the Ejecta plugin is open source? Since the file-reader plugin will probably never work with Ejecta, since it is a DOM element.