We migrated to the new build servers as mentioned in the blog/social media
repeatedly.
This has temporarily cut our build server count in half, we hope to migrate
legacy servers over this to next week to use xcode 7.x.
--
You received this message because you are subscribed to the Google
If you don't use a browser component this has no effect.
If we do that it will impact everyone who uses a browser component which is
probably not what they would want...
If you DO use the browser component you can call these methods using
setProperty(). So this is available for real world
Hi,
Still prohibited by Apple.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to codenameone-discussions+unsubscr...@googlegroups.com.
Visit this group
It was implemented ages ago, it is under the Codename One menu.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I don't actually want the menu to hide / show, I want it always visible,
but if I have commandBehaviour=Bar and a Toolbar I always get a Side Menu.
On Monday, August 29, 2016 at 5:24:06 PM UTC+12, Shai Almog wrote:
>
> Not with general customization.
>
> The menu is wired to the overflow. Some
I've been made aware of some issues on my QRScanning library and looking
into this now its the same issue here as well. onActivityResult is never
called.
Going back though build and testing logs it looks like this was working
fine on builds that were created two weeks ago, some time between
I am experiencing the same problem. The onActivityResult function in
AndroidNativeUtil.startActivityForResult is not being called.
On Monday, August 29, 2016 at 11:39:45 PM UTC-5, Shai Almog wrote:
>
> I'm not aware of any major impacting changes to the Android build
> toolchain in the past few
My IOS build times have suddenly doubled. Now clocking in at nearly an
hour.
I suppose you've upgraded your servers again and there's nothing to be done,
but just in case you aren't aware, it's a problem.
--
You received this message because you are subscribed to the Google Groups
The IOS requirement to use this build hint to permit HTTP requests seems to
have kicked
in today. I'm not sure if this is because of something apple changed or
something codenameone
changed.
ios.plistInject
NSAppTransportSecurityNSAllowsArbitraryLoads
No word yet on if apple will start
Local notifications will continue to be delivered as long as the user
doesn't explicitly quit the application. If the user explicitly quits, the
interpretation is that the use doesn't want to hear from that app anymore.
On Tue, Aug 30, 2016 at 4:33 AM, Bbeck Shrestha
the notification appearing in the background and not while app is in
foreground is totally ok. But i am concerned if the local notification
appears while app is closed (ie. not in both foreground as well as not in
the background?
--
You received this message because you are subscribed to the
the notification appearing in the background and not while app is in
foreground is totally ok. But i am concerned if the local notification
appears while app is closed (ie. not in both foreground as well as in
background?
--
You received this message because you are subscribed to the Google
12 matches
Mail list logo