Since we are all good programmers we never make mistakes, right ? 🙂
But for those times when you write some code and you just can’t figure out why its not behaving, there is always the Debugger!
The best part is the Debugger is very easy to use and it can help you sort out a lot of common issues. Its covered in the Xojo User’s Guide, specifically see the Using the Debugger section.
The first classes in the new Xojo Framework have been available for all project types since Xojo 2015 Release 2. Here are some of my favorite features.
With many things in life, more choices means more freedom of expression. We can pick and choose what we like personally as a way to express ourselves. Such is the world on Linux. The myriad of different Linux distros along with all the different Desktop managers and Window managers available are daunting. While more choices is nice (in general anyway), it can also cause more confusion. As a cross-platform developer, you’re probably aware that every operating system has their own way of dealing with crashes and crash reports. Â On Linux this is no different, but it is more confusing because not every Linux distro plays by the same configuration. This blog will answer some fundamental questions you may have about what happens when your application crashes on Linux.
I’ve been working with JSON in the new Xojo framework quite a bit lately and wanted the ability to format the JSON text so it is more readable.
A little Internet research turned up a set of classes for .NET (in C#) that can do this. I took a few minutes to port these three classes over to a single Xojo class that can format JSON for you.
Eric Gibbon has been using Xojo to develop bespoke cross-platform applications for Mac and PC and for the web for 15 years. He lives in Stamford, England, and is an active member of the Xojo UK User Group.
There’s an old programmer’€™s saying: If it works, leave it alone.€ But sometimes we have to go back to code that works to make it go faster, because it’€™s too slow.
Over time I have picked up some tips on how to get better performance from Xojo code. I have used these tips to improve old code running on all platforms and have seen big improvements. They are quick and easy to do.
If you work with computers, having backups of your data is essential. This particularly came to light recently with people testing out Apple Music and discovering that it could make a mess of your iTunes library. In fact, this happened to me!
But “luck favors the prepared” and I had backups, so this Apple Music glitch only proved to be an annoyance and not a catastrophe.
In my case, I just restored my iTunes library from my Time Machine backup. But I know far too many people that don’t even have any type of backup system in place. I’m here to help.
Anyone who is developing software, even if they are the only person working on the project, should be using source control (aka as version control). As you can see, this comes up a lot:
The code editor tries to help you see what code groups together. For instance, it draws small lines between matching block beginning statements like IF, SELECT CASE and their closers (END, END IF or END SELCT):
Though increasingly rare, we do still hear from Xojo users who get false positives from their anti-virus software when downloading Xojo or running Xojo applications. We’ve even heard of this occurring when users are debugging apps from the IDE. To get around this, you can refer to the documentation for your anti-virus software on how to exclude Xojo from scans. To fix these issues for yourself and future Xojo users, we ask that you report these occurrences to your anti-virus software makers.
We’ve occasionally heard from Xojo users that their anti-virus software gives them a warning about Xojo. All of these have been false positives and we ask that you report these to your virus software makers if it happens to you.