[codenameone-discussions] pull to refresh not working on tab component
tested in the simulator with the below code, pullToRefresh runnable is not
getting called
Form hi = new Form("Hi World");
hi.setLayout(new BorderLayout());
Tabs t = new Tabs();
t.addTab("Test1", new com.codename1.ui.Label("Test1"));
t.addTab("Test2", new com.codename1.ui.Label("Test2"));
t.setScrollableY(true);
t.addPullToRefresh(new Runnable() {
@Override
public void run() {
System.out.println("Tab Refresh");
}
});
hi.add(BorderLayout.CENTER, t);
hi.show();
I dont necessarily want the tab to be pull to refresh, but only the content
of tab "Test1" which is actually a container.
--
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 at https://groups.google.com/group/codenameone-discussions.
To view this discussion on the web visit
https://groups.google.com/d/msgid/codenameone-discussions/2dd5c516-d183-4115-a59f-bfa480c75eab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [codenameone-discussions] Re: Windows build only runs as background app
Thank you for the command line option. I used it and uncovered that Steve
was correct in the assumption that my app is throwing an error. I have
added a few debug output statements to help me identify the exact line that
is hanging. Let me give a few pre-qualifiers to the scenario.
1) my app uses a standard splash screen which runs some initialization and
registration checks
2) these checks are inside the postSplash function and the splash screen is
never displayed
3) i make use of a "loading" label object to show status messages to the
user
I suspected that my app would be hanging on the "loading" label
object modification statement of:
statusMsg.setText("Opening Registration System...");
but strangely enough it makes it past that line to hang on the next line:
Dialog.show("Device Registration", "We will need to perform registration
before you can make use of this application.", "OK", null);
I can see how both these lines of code could be problematic when the app
hasn't actually come into view yet, but I can't understand why the app
hasn't come into view yet.
On Tuesday, July 5, 2016 at 5:38:34 AM UTC+1, Shai Almog wrote:
>
> Try running the project from command line using java -jar with your jar
> file name. It should be somewhere in the installation hierarchy.
>
--
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 at https://groups.google.com/group/codenameone-discussions.
To view this discussion on the web visit
https://groups.google.com/d/msgid/codenameone-discussions/c524063e-f4a0-4ea4-b714-cb6cc9892a2d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[codenameone-discussions] Native interface not work after AlarmManager/onReceive in Android 6.0
Dear Sir,
On Android 6.0 when I wanna do AlarmManager and onReceive, it is quickly
found out that of the Doze mode issue, the "setRepeating" is not work but
using "setExactAndAllowWhileIdle" instead ( or may use
"setInexactRepeating") so that the receiving is successful. Afterwards when
i call the native code function, the native code function is not work
anymore and the application will be suspended.
e.g.
After calling
public void setScheduler(Context context) {
//.
am.setExactAndAllowWhileIdle(AlarmManager.RTC_WAKEUP,
cal.getTimeInMillis(), pi);
//.
}
Then
public void onReceive(Context context, Intent intent) {
//...
Intent mainUIIntent = new Intent(context,
MainUIStub.class);
mainUIIntent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
mainUIIntent.putExtra(LAUNCH_BY_SCHEDULER, true);
context.startActivity(mainUIIntent);
//.
}
Then in MainUI
public void start() {
//.
MobileNative mobileNative = (MobileNative)
NativeLookup.create(MobileNative.class);
if (mobileNative.isLaunchByScheduler()) {
Form gui = stateMachine.showForm("FormMain", null);
gui.getMenuBar().removeAll();
}
//.
}
When i call the native function "mobileNative.isLaunchByScheduler()" which
is used to just return true, i can see it can go into the native function
but cannot return and the application is suspend here.
Would you have any suggestion and what is the codename one response for the
android 6.0 change for Doze mode issue?
Thanks and Regards,
Ronald
--
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 at https://groups.google.com/group/codenameone-discussions.
To view this discussion on the web visit
https://groups.google.com/d/msgid/codenameone-discussions/cc1c5177-23b6-4f05-8604-a2c3fb9afd2c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
