I've searched Google for about 1,5h now and i can't find a good answer.
Is it possible to display the Soft Keyboard when debugging using ADL?
If i use the existing properties I still don't see it.
I want to check if my layout looks well when the Soft Keyboard appears, but for some reason I don't see it coming in ADL (Adobe Debug Launcher).
I don't have a tablet to test it on for now so that isn't a solution.
Am i doing something wrong whereby I don't see the soft keyboard or doesn't it exist in ADL?
ADL is just the Flex debugger program. When I use ADL to launch my app on an Android device; there are no issues getting the soft keyboard to show up. When I use ADL to launch an app in an emulator, I have never seen the soft keyboard come up. This is not supported with the emulator included with Flex / Flash Builder.
In my experience the availability of the soft keyboard depends on the context you're running the app in (Debugger vs Device) and has nothing to do w/ ADL.
Does that answer your question?
Related
I have a XF app already published on the play store and now I am targetting iOS. During developpent I made sure the app was still working on iOS, using the simulator only.
On the simulator everything works as expected, the launch screen is shown then the MainPage starts. But when I debug on an actual IPhone device, the app get stuck on the Launchscreen.storyboard for about 20 sec then the app exits. I've no debug output and it seems that the AppDelegate is never hit. Breakpoints in AppDelegate.FinishedLaunching method are not hit for instance. I tried to F11 for start in debugging mode but I don't hit anything, still hanging on the launch screen. I was expecting the transition from simulator to device to be less painful.
My plist file contains the following permission requirements
...
<key>NSLocationAlwaysUsageDescription</key>
<string>We need to use your location</string>
<key>NSLocationWhenInUseUsageDescription</key>
<string>We are using your location</string>
<key>NSPhotoLibraryUsageDescription</key>
<string>This app needs access to photos.</string>
<key>NSPhotoLibraryAddUsageDescription</key>
<string>This app needs access to the photo gallery.</string>
The only difference I saw is that location permissions are not asked on the device while in the simulator it asks for it at start. But this might be related to the fact that I can't reach AppDelegate, I am not sure yet.
The iOS project was generated via Prism templates. I am using VS 16.8.0 on Windows, XF 4.8.0.1687, Prism 8.0.0.1909, Xamarin iOS SDK 14.4.1.3 and I am set to "don't link" for linkers option. The device is an Iphone 10.
Any idea how can I find out the root cause - or get some useful logs?
Thanks in advance for your help.
EDIT:
Here are the device log output during a new installation https://taits.s3-eu-west-1.amazonaws.com/devicelogs.txt. I am trying to go through them but kinda lost.
Currently I am writing iOS tests using Python Appium and would like to completely hide the software keyboard which pops up whenever you have to type something. I am already aware of driver.hide_keyboard() function but it's a pain to include it everywhere in tests.
I was going over the Appium Desired Capabilites but couldn't find anything that will disable the software keyboard. Appreciate if anyone can help me here?
To disable soft keyboard in iOS simulator do this:
Simulator Menu > Hardware > Keyboard > Connect Hardware Keyboard (enable it)
Even if you quit and reopen the simulator, the selection will stay. I'm not sure what happens when you factory reset the simulator.
screenshots attached.
For a kiosk application on a touch screen device we use a web app running inside chromium browser in kiosk mode (--kiosk), which implies full screen. We are now seeking a solution to provide users with a virtual keyboard.
What we have tried:
Chrome-Extensions: There are a lot but all of them seem to fail as soon as an input field is inside an iframe, which makes them unusable for our scenario
Linux virtual keyboards ( We are on Ubuntu 14.04 / Openbox window manager) : Florence, Onboard, matchbox keyboard, tried any I could google ;-): They all fail as soon as the browser is in full screen mode.
Javascript / jQuery Plugins: see above / Chrome Extensions (iframe problem)
So the question is: Is there a way to tell Openbox (or another window manager, switching to another wm could be an option) that the keyboard window should be placed above the full screen browser window? Or any other suggestions are welcome.
The closest solution right now is to run chromium not in kiosk mode but maximized without window decorations (so it looks like fullscreen), then "Onboard " is a good choice, but all the other features from kiosk mode (e.g. disabled context menu etc.) are missing...
Thanks a lot for any ideas on this subject!
Ive been trying to add a button to properly exit an Android app, built using Flex 4.6. I have used the command NativeApplication.nativeApplication.exit(); which seems to work on the emulator, and kills off the emulator.
When I run it on a device, it doesnt exit, it actually seems to go to start of the app (my login screen) which is kinda strange.
I hypothesise that something system-wide is holding the app in process or re-starting it. Anyone had any experience with this?
That code should work. I use it in my android flex app with no problem. The application quits correctly and I am dropped back at the home screen. What version of Android are you using? I was using 2.3 when I did this. If you have it running in debug mode, do you see any errors output to the console? Using the debugger will also allow you to see if it is not quitting properly or restarting on quit(you would see the splash screen again if this was the case)
I have installed Flex Builder 3 and Flash Player 10 on my machine.
I don't know where the trace output goes because I just don't see it (I tried debug and output windows).
Also the breakpoints don't hit.
Salut Omule :)
If you press the Debug Icon(the bug thingy) or go to Run > Debug you should go to the Debugging perspective.
If might be handy to install the Flash Tracer plugin for Firefox to see your traces from the browser.
First you need to make sure you have the Debug version of Flash Player 10. You can do that by checking is Debugging is true using this test.
You can view traced messages in the console (Menubar - Window - Console).
But since you said that breakpoints are not hit, I guess the problem is somewhere else. Make sure that you are debugging instead of running the app (select Debug from the Run menu or just hit F11 while at the corresponding mxml file).
If that doesn't help, and if you are on Firefox, try uninstalling the last addon that you installed. Some addons (including older versions of google toolbar and adblock plus) have known to block swfs from connecting to the flex builder's debugger.