#Xojo weblistbox sort code#
Windows IDE: code editor no longer flickers in certain edge cases when moving the text cursor or moving the mouse over particular source code items PrinterSetup.OpenPrinter (or OpenPrinter) no longer raises a failed assertion if the user cancels the open printer dialog Controls are now refreshed properly when the App is being run inside a remote desktop session with different screen sizes It is a decade of neglecting bugs (due to being understaffed? Company culture?) that brought on their problems in the first place.- Fixed regression on Debugger Filter showing duplicates first time a break point is hit when the project is run on Windows iOS and Web have not brought them the success they’ve hoped for. I do feel their pain and I understand the pressure they are on to release new stuff. Looking at the lists of bugs in an other topic on this forum (from only 2 users I believe?), it must be overwhelming for the Xojo engineers to start fixing them.
#Xojo weblistbox sort software#
Anywhere Software has investment injections from a large company since a couple of years now, which did even allow them to make their showpiece B4A (Android) completely free. Having a Mac/Linux IDE will not dramatically increase that number IMHO and if it would force the current IDE to take steps back to support them, I rather they don’t. The user base is many times the one from Xojo.
That alone is a breath of fresh air compared with Xojo’s bug fix quality.ī4X is RAD and very much alive. With our current IDE (B4X) we get a similar courtesy from its developers. And if one does come up in a released version, they are almost always fixed withing 24 hours. We do extensive testing (almost 30% of the total development time). They used to be great a that, nowadays they are just mediocre.ĭo we have bugs in our software? Yes, but very few of them ever reach the end-user. As said before, they should’ve sticked with desktop only.
#Xojo weblistbox sort android#
Having to restart from scratch three or four times on the Android framework (Geoffs words) should’ve been an eye opener. I sometimes seriously doubt Xojo has enough in-house knowledge/experience on WebApps (and iOS/Android for that matter). It should’ve been build in stock Web 2.0 from the very first release. Mike D on TOF showed with FastStart it is possible in Xojo, and his implementation should be general knowledge for someone who writes WebApps.
First-loading times are terrible (loading lots of stuff that is never used in the final WebApp) and caching is hardly fully implemented. Xojo’s Web framework design is flawed (mostly their event system) and is way to slow to satisfy our clients. Unfortunately, Web 2.0 is far from ready for larger web projects. Offline PWAs are not possible in Xojo, but I did have a good look at Web 2.0 in case being able to work offline was not a requirement for some of our clients as we did have a vast library of logic Xojo code we hoped to be able to re-use. For our company “slow” is, although not a bug, certainly a showstopper.
0 kommentar(er)
