I am creating my first Adobe Air application from a Flash animation file via Flash Builder (I am an Android developer by trade.) One of the last updates I had to make was updating some of the text fields within the app to be dynamic so their text can be set at runtime via ActionScript.
When I view the app via the Adobe Air Simulator or push to an iOS device the buttons work fine, but when I push to an Android device some Buttons and Movie Clips are invisible. I can still click on the buttons if I touch where they should be on the screen but I cannot see them. In my testing of a fix I set the alpha of a button which is affected by this issue to 100 but it still shows as invisible.
Is this a known issue? How would I go about ensuring that all Buttons and Movie Clips are visible to the user?
Thanks,
Adam
Edit:
The only change to my code in order to set the text is running the following AS:
play_play.text = TranslationUtils.getTranslationText(TranslationUtils.PLAY_PLAY);
The AS for the TranslationUtils class is an external AS file which switchs through constants to return the correct text, based on the device's Capabilities.language
Related
I have an Android app built with Delphi 11.2 that works fine on the devices. However, when I submit the app to Google Play Console for testing, their auto testing reports warnings about Accessibility problems. The Pre-Launch report has a red rectangle highlighting the full screen of the app under the Content labeling section, with the recommendation "This item may not have a label readable by screen readers."
So, I started up TalkBack on my Android device, and it does the same thing. It shows a blue highlight around the whole app screen. If I try to press any of the buttons on the screen, I hear a beep and the highlight remains around the whole screen and nothing happens. It is like there is some object overlaying the whole app screen and not allowing access to any of the controls under it.
When I look at my source code, the only items that cover the full screen are the form itself and a TLayout item set to Client of the form. All of the controls are placed on top of the TLayout.
Has anyone else had problems like this with Android apps build with Delphi? If so, what do I need to do to fix the problem for screen readers not having access to the controls?
I am creating an App for Dual Screen by using Presentation API for showing a separate view for Customer, in which there is an input field (EditText), which asks the customer to input depending on type of fields. Now, the issue is that the softkeyboard only appears on the main screen & not the secondary screen, due to which only the person facing main screen will be able to input values in EditText. But I want to open softkeyboard on both sides, not both at the same time and atleast they should be able to open it one at a time.
If I try to forcibly open the keyboard it still opens on the other side (main screen) only.
If you were using Android 10:
From:
https://developer.android.com/guide/topics/ui/foldables#software_keyboard
Software keyboard
A keyboard can be shown on a secondary screen if the display is configured to support system decorations. The input method editor will automatically show up if a text field requests input on that display.
While leads to:
Android Open Source Project - Input Method Editor Support
https://source.android.com/devices/tech/display/multi_display/ime-support
and that page has a lot of detail on the various implementation & security issues on having a multiple display IME.
As you mentioned a custom device running Android 7.1 unless the manufacturer has modified for system decorations:
From that AOSP page on IME support:
In Android 9 (and lower), the IME was only available on the default screen...
So from stock AOSP you can't have the native IME appear outside of the default display.
I can only suggest reaching out to the manufacturer to see if they have a custom SDK for that feature, else you will have to create your own IME-like view, assuming you can get touch events from the secondary display.
I am trying to make the default tock sound work when you click something in an app, but I have not come across a way to do it without recoding a lot of the app. Specifically, I am looking if a button is pressed I want it to make a sound. When I'm on my android for example, if I'm in Fb or gmail when I click something it makes a sound. I am using Ionic 1.2 right now for the app. Even when I use an emulator, it doesn't seem to make a sound - and it definitely doesn't do it in ionic view
For large size screens, the default android keyboard automatically displays Tab keys. I have a phonegap application which contains several input boxes on one page. When I try to navigate between input boxes using tab key on soft-keyboard, nothing happens.
I also tried to open gmail login page on browser and Tab key didn't shift focus there as well. However, I noticed that only in case of input boxes, I had to use shift+tab key to navigate to next input box. For navigating between other elements, just pressing tab key was sufficient. Is this the specific behavior implemented by android & is there any particular reason for it? I am using nexus 10 but found same behavior on emulator too.
I think this is a problem with Nexus 10 in particular, as I observe the same thing and here is another user that reports the same (https://stackoverflow.com/questions/16651669/nexus-10-keyboard-tab-key-not-working).
Tab key does work on native Android apps as it is supposed to, but not on hybrid apps which are basically wrapped in WebView. I think this is an oversight from the Android team. You can always install a Swipe or Hackers keyboard from the Play Store where the Tab key does the job.
This seems to be an issue specific to Android Tablet devices. A workaround I found was to change the keyboard mode to either split or floating. Also I noticed flipping the device around to landscape view allows the input elements to behave correctly.
The original issue is related to the viewport size change that happens when any input receives focus which is caused by this so-called soft keyboard. Android seems to handle the rendering of a soft keyboard differently from other manufacturers.
I have an enterprise Flex web application, served up over https, that runs fine on Flash player 10.0 and beyond on a desktop computer/browser.
However, when I run it from my HTC Incredible with Android 2.2 the app loads fine, but there is no on-screen keyboard and so I cannot log in. I can see the blinking cursor inside the username and password text fields. I can switch between them. I can even hit the login button and see an authentication error!
According to Adobe this should Just Work. Any ideas? I wanna show off our spanking new app to strangers at the bus stop!
Seems the problem is different implementations of the keyboard in the browser. See the comment from Adobe here as they shut the bug as unfixable: https://bugs.adobe.com/jira/browse/FP-5704
I have the same problems on a Galaxy S2 - though manually forcing the keyboard up here isn't an option as the address bar automatically gains focus.
Mobile Text Input
Flash Player 10.1 provides support for use of native device virtual keyboards with TextField support if no physical keyboard is detected. A virtual keyboard is automatically raised and lowered in response to focus changes on text fields when editing text on mobile devices supporting a virtual keyboard to enable unobstructed and intuitive text editing. The focused text field is centered in the visible region of the page and appropriately zoomed/scrolled to ensure it is not obscured by the virtual keyboard. Upon screen rotation, incoming calls, or other system events, any already existing text input is retained. The virtual keyboard works with TextField but does not currently work with the Text Layout Framework or other Flash Text Engine text.
The spark components in Flex 4 are not currently optimized for mobile. The next release of Flex codenamed "Hero" will provide mobile optimized skins for the spark TextInput/TextArea components. These skins are based on TextField and they are also optimized for performance with ActionScript skins and a more appropriate default size. Text support in the current Hero preview release is minimal, but the final release will be more robust, for example supporting scrolling in a TextArea. Check out the spec for more information: http://opensource.adobe.com/wiki/display/flexsdk/Mobile+Text+Components
It's probably worthwhile to note that the mobile features in Hero are designed with standalone mobile applications in mind, not browser-based applications. That said you might be able to grab those mobile skins and try using them in a browser-based Flex application compiled with Hero.
have you tried republishing your work strictly for 10.1? i believe that any applications which support versions of Flash prior to 10.1 are seen as Flash Lite on mobile devices, which may (or may not) be the problem.
it's worth a try.
Not a programming solution, but long press on the menu button brings up the keyboard if it doesn't pop up by itself (at least on my HTC Desire, 2.2 android).
Device: Kindle Fire
I had the same problem. My mathlab uses flash for homework assignments, and I could not access my keyboard for input. Until I found this.
Download and Install "Keyboardflash_1.0.0.apk" on your Android device.
go to the flash program in your browser
run the "Game Keyboard" app and click "Tap here to call out keyboard after exit"
return to your browser
You will notice I did not perform the direction the app gives you because the kindle fire is not compatible with those steps. Maybe it is with your device.
You may have trouble getting this to work with a browser app like "Dolphin"
Your Welcome :)
and respect the developer
Gamepad is also on the android market.