This is something that is getting rolled out on all new. The last thing Xojo implemented for the Windows target: WindowsUniversalRuntime. NET to follow the HiDPI support, but guess what - no such chance. You would think that this would mean the WIN target will move to. There are a number of odd things with that one (only under Windows) and it seems they may get chucked to the fact that the executables are still WIN32 and not. HiDPI for Windows also seems to be BETA, even though Xojo does not call that one BETA. 64-bit on WIN apps is (how should I say), BETA (to use Xojo's own words), sometimes you compile the app and get one behavior, another time you compile it and get a different behavior (did I mention misgivings with the compiler for the Windows target already?). Let's be reasonable here, Windows only got 64-bit and HiDPI because Xojo had no choice, they had to deploy these for the MAC (even though Windows OS has had HiDPI for many years now) and it shows. Xojo recently implemented 64-bit and HiDPI on both Mac and Windows. That affects WIN apps in the following ways: controls flicker (a lot in some cases), many "native" controls look VB6-like, no touch support, transparency is hit and miss. It still uses the Win32 controls and libs, and has no support for. Xojo has not touched the Windows platform in over 10yrs and it shows. So if a simple app cannot be optimize, you know what to expect form heavier apps (and that shows on the multiple issues Window users report on the forum about crashes and such - on Windows). Why you ask because XOJO does not optimize code on the same way native tools do. A more complex app, well is bigger than 50MB. SOLID 2.ĭon't get me wrong, you can create a Windows app that looks and runs ok. Ok support, hasn't been touched in over 10yrs (with a couple of exceptions that I will describe next), applications look old (unless you use additional 3rd party plugins), applications are huge (will describe next), does not shine. Good support, still evolving, still a pain to deploy, applications look kind of low-budget and cheap (unless you get additional 3rd party plugins or use a lot of declares to work with native controls). A 64-bit math application for the most part will be slower than a 32-bit application (plenty of examples on the forum, for those who may not believe such thing is possible).Įxcellent support, constant updates, streamlined applications bundles, can create fast and snappy applications, truly shines. Compiler seems more of an interpreter than a real compiler in that there is very little optimization. In a few of the "supported" platforms, a standard application will require 3rd party plugins if it is to look modern by any extent. It is on the type of applications, the look of the applications, and the support to each of the platforms that things differ. It indeed allows you to create cross-platform applications with relative ease. ![]() Documentation Window > Documentation: Navigating with the Back/Forward buttons now behave correctly instead of intermittently.Framework > All: DatabaseRow: Double values now preserve the same 20 digit decimal place precision that RowSet Double values do.Framework > All: Now PDFGraphics.DrawLine honors again the starting and ending coordinates when drawing diagonal lines.Miscellaneous: Now correctly loads the MSOfficeAutomation plugin (especially the Office module).IDE > Layout Editor: Dragging a Timer onto an iOS MobileScreen now correctly adds the Run event handler, instead of the incorrect Action event handler.IDE > Auto Complete: Properly show deprecated Array methods in autocomplete in older projects.Framework > iOS » Mobile: Graphics.DrawPicture no longer cuts off part of the image when specifying all parameters.Framework > Web: Fixed a visual issue while using.Framework > Web: Fixed an issue with WebLink that was not truncating long links.Framework > All: Using Dictionary.HasKey(), Lookup(), Value() and Remove() with an empty Text key value no longer crashes on Windows/Linux.Build: Reduced non-Universal macOS app size by stripping unused architecture parts from the final build.
0 Comments
Leave a Reply. |