Hi, it's a bit hard to implement that full API. A more pragmatic approach is narrowing this down to an RFE about specific classes/methods. We might include some features of that ideally in the Codename One packages to keep things simple as changing the VM takes much longer than implementing a small subset in our own packages.
Notice that this matters more for server processes. On devices you shouldn't use too many threads anyway as there is a limit to the number of cores a device would have. FYI we have FYI check out EasyThread which makes working with a separate thread relatively easy. -- 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 [email protected]. 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/7dbab572-e6b0-4e3c-be2c-6430573cf83a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
