If you kept the logs but not the builds, you'd have a lot more headroom.
Also, it would be useful (in this case) if the "save sources" went ahead
even if the build failed.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To
If they were long enough we would run out of storage space, there is some
information but it's not immediately available.
--
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's this issue:
http://stackoverflow.com/questions/40546461/codename-one-uwp-build-failed
Only with the code scanner cn1lib. We need to do an overhaul now.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this
Sorry had my wires crossed with a different question on media.
You don't need a UITimer in this case, just fire a callSerially when a
batch of data arrives
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this
Assuming you have multiple servers, is there any information that would
identify
which one was used in this particular case? An obvious piece of
information to
look for would be if the failed builds were all on the same server.
--
You received this message because you are subscribed to the
I assume you're referring to some other log than the one I have access to.
You ought to keep your logs long enough for them to be useful, but in this
case I assume
the most useful information would be to retrieve the culprit
com_codename1_ui_Component.m
which would be long gone.
--
You
You need to keep your logs long enough for them to be useful.
--
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
Just tried a Mobile Debug build, same problem.
--
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
A policy question. As of now, it's been 16 hours since you tacitly
ackknowledged that IOS builds are seriously broken
by a recent update. I know "stuff happens" but your build servers are
still building, still producing the bad builds.
Shouldn't there be something in place to either turn off
If the long poling connectionrequest(with addtoqueue)which has a default
timeout of 60 sec is fired inside uitimer?!?
Will it freeze or slow UI. If yes, what is the best way to handle.
On Saturday, November 12, 2016 at 6:15:46 AM UTC+1, Shai Almog wrote:
> If you keep it at 1 second interval
I vote for native look and feel versus consistency across platforms. I
understand the point but I would rather my app looked like a real Windows
Mobile app.
I do actually add the back button on Windows but on the form level:
_backCommand = new Command(Prefs.getMsg("rw.msg.nv.lst"));
Meantime, anyone who is using 2d arrays is shipping bombs.
--
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
Yup, that looks like the right place. Bummer that it was a fix to a purely
theoretical problem that I reported.
Q/A is a bitch.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving
13 matches
Mail list logo
