Alloy left/right keyboard events ScrollableView - titanium

I'm building a titanium alloy app and I'm using ScrollableView to show different pages of the app. I have set showPagingControl="false" and scrollingEnabled="false". Its got a basic login code so when the user is valid it goes to the next page.
I just realised that focusing the scrollableview and using keyboard left/right buttons changes the page which isn't ideal as the user isn't meant to be logged in. Is it possible to disable this?

I'm marking this as resolved as I think it was an error in my emulator

Related

Appium iOS can't inspect notification layer

Im using Appium to test my notifications in my iOS app.
Im sending with another device a notification while the iOS app is in BG. Then I swipe down using :
((IOSDriver) wd).swipe(500,0,500,1000,1000);
The above works, the screen get scrolled down and I can physically see the notification. The issue is that the appium still inspects the screen below.
I checked appium inspector and it verified that it doesn't recognize nothing but the elemnts of the layer below the notifications one.
Any approach ??
As long as I know it is known limitation for iOS now.
You can get notification bar elements on Android only
But based on top comment it should be possible to wrap up with Appium since Xcode 9 introduced interaction with multiple apps, so its matter of time.
I found a workaround that fits my needs.
I found out that if I click the home button and then swipe down the notification are visible to Appium.
Because Appium not having key events for iOS, iPhone has the an accessibility option for home button, I toggled that on and I can simply click it during the test and swipe down the notification center.
I know it's not ideal but its working.
Thanks for the help.

Shoutem builder preview not working

I'm trying to preview the app after making changes to the built in extensions. When i try to preview the app it tries to build the preview but ends up doing nothing and and brings back the same original screen. I'm not getting an error message at all. What could be the issue?
Here's a great tutorial on how to modify extensions. why I think it's not working for you is because you didn't change the starting screen inside of the navigation. The previous screen that you use is from original extension. You need to click on the three dots in the upper right corner to delete the Screen.
Here's the picture:
Once you've deleted screen, add your screen from Custom category.

Graphics.CopyFromScreen just my app window

I am using copyfromscreen to show a modal please wait message.
It works great but i find it failing when I'm doing alt tab to the app or I'm looking to another app and come back to my application.
Original post I got the idea from:
Javascript Like Modal Window for WinForms
I was curious if there is a function that would let me get screen capture of my app only even when its hidden in the background.
Control.DrawToBitmap Cody Gray suggestion actually works. Just grab the forms bitmap instead of doing full screen grab.

Prev and next buttons for pickers in Sencha Touch 2

I'm building an App for Android, iOS and Blackberry with Sencha Touch 2.0.1.
I have a Form-Panel with about 10 selectfields and some sextfields. If i ran the app on Android 2.3 or higher, the selectfields are shown as pickers. So far so good.
When the user starts filling out the form starting with textfields, he can go through the form using the next-button on the virtual keyboard. The problem is, that the selectfields are ignored by the next-button. The user has to tap on the selectfields.
I can't figure out how to get prev- and next-Buttons for the picker-elements. So that I can go through the form only with the next-Button instead of pressing "done" and tapping on the next Selectfield. It would be far more comfortable for the user.
So support of the sencha-forum isn't really helpful, see below:
http://www.sencha.com/forum/showthread.php?219636-Native-select-field-for-Android
http://www.sencha.com/forum/showthread.php?205581-Can-I-use-iOS-native-picker-instead-of-ST2-picker
According to this, there are prev- and next buttons available for a picker:
http://www.sencha.com/forum/showthread.php?205159-Ext.picker.Date-with-no-prev-and-next-buttons&p=803794
But I can't find them:-(
I think, there are two solutions to the problem:
Accessing the native Picker as proposed in the first link above. The question is how?
Implementing an own Picker-Element with an Prev- and Next-Button. This seems to be a huge efford for such a basic task.
I can't really believe, that this is such a big deal in a big framework like Sencha Touch.
Anyone facing the same problem and has a working solution?
My only idea for you would to put your picker on the page as normal, then add two buttons on the page - a Prev and Next buttons using Sencha. Then add onTop handlers for those buttons, that use the picker's .setActiveItem() method to set the picker to the next or previous item. Hopefully that will get you on your way.
http://docs.sencha.com/touch/2-0/#!/api/Ext.picker.Picker-method-setActiveItem

Rubymotion implementation of the previous/next buttons in the webview

I'm new to iOS development and recently started out with rubymotion.
Im currently working on a "start page" kind of application that loads an in app html/css/js file in a webview. The "start page" then links to different sections/pages on (a to be released) responsive design version of http://hiof.no .
My current build of the app is based on the PaintHTML example:
https://github.com/HipByte/RubyMotionSamples/tree/master/PaintHTML
The feature I'm stuck on at the moment is previous/next page navigation to navigate back and forth in the webview history.
The idea of the navigation feature is to have previous/forward buttons positioned fixed on the bottom left side of the app similar to the Path app "new content" button.
Any ideas how I can implement access to the webview history with "native" rubymotion code?
the UIWebView have to methods UIWebView#goBack and UIWebView#goForward,
create two button and set the action to #webView.goBack and #webView.goForward; and you can enable the button with the methods [UIWebView#canGoForward and UIWebView#canGoBack]
Documentation