I think you have unreasonable expectations. I spend a lot of time supporting and trying to help regardless of your subscription status. We do resolve a lot of issues for all subscription levels but our general rule of thumb is about blockers and big issues. This is a big issue for you but it isn't for anyone else. Most people don't mix HTML and Java code too much. These have always been the difficult edge cases in every platform that mixes those. Yes CEF does have issues but those issues are limited to the simulator for the most part. On the device the implementation has been the same for years and literally no one complained about the problem you ran into. Since it happens on Android you can debug this using Android Studio. I don;t know if it happens on iOS but I repeatedly made it clear that you need an iOS device and need to test iteratively. There's a limit to working with the simulator and when you work heavily on native peers (and HTML is a native peer) you need a device.
On Tuesday, March 9, 2021 at 9:48:34 AM UTC+2 P5music wrote: > Already done debugging on Android in regard to this: > BrowserComponent: mouse events handled differently in Android device than > simulator (google.com) > <https://groups.google.com/g/codenameone-discussions/c/121OlNeKXh0> > > Mouse events for long press are not working. I filed an issue. > It seems that you released the CEF without even bothering to check some > HTML-Javascript content inside. > > Now I cannot publish my app because the very first functioning of a > BrowserComponent is not available. And I already wasted a month of Apple > developer program, not mentioning being on this project from June 2020. > > I have a free account but one could look at it from a different > perspective: you released a new feature without any testing and luckily you > have an early tester for free. > But you are not listening to it. > > When I subscribed as CN developer I received an e-mail saying like "please > help us to spread the use of the CodenameOne" or something similar. > But how are we supposed to help if you do not fix issues of such > importance, that are already deployed in fact. > > Believe me, many times I returned to my Swift project, not difficult to > update it because a few lines of development were possible for me to do in > months with this very painful day-to-day before-going-bed "free" assistance > you think is doing good for CN here and on StackOverflow, > > but Swift/SwiftUI is so awful that I had to continue with the CN project, > > that I like, do not misunderstand me, it has many avantages I want in a > project, > > and I believe in having an easy way to develop for iOS without > surrendering to Apple. > This it the "plus" of CodenameOne, not the cross-platform stuff for > Android or Blackberry or desktop. > > How do you see it? > Regards > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/3a28e0af-4471-4a65-9822-1899b644e4e9n%40googlegroups.com.
