Often when debugging an application, you’ll need to enter the same data in the same fields over & over. There is a temptation to set the value of the field to the test data. The downside of this is that you need to remove all those defaults before deploying your application.
At XDC 2019, I did a session called Avoiding Troubleshooting Troubles, which was essentially about ways to take advantage of the Xojo debugger. During the…
Here are a couple tips you can use with computed properties.
Viruses continue to be a big problem on Windows. As a result, anti-virus software can be a bit over-zealous about detecting what it believes to be apps that have viruses embedded within them. We have had reports over the years that apps made with Xojo are sometimes falsely identified as being infected with a virus. This sometimes occurs because the 32-bit Xojo compiler puts executable code in a location where the anti-virus software doesn’t expect to find it. We’ve seen this occur even when users are debugging apps from the IDE. Fortunately in that case, there’s a fairly easy solution.
In his poem, “The Mouse”, Robert Burns wrote:
The best-laid plans of mice and men oft go astray…
As Burns so eloquently stated, no matter how carefully you plan sometimes things just don’t work out. Anyone who has done software development for long knows this all too well.
Using the Remote Debugger means that you can run Xojo apps on the Pi for testing and development without have to first purchase a Xojo license.
You can set breakpoints in your Xojo code that cause the debugger to appear when the line of code with the breakpoint is reached. This is incredibly handy to help understand and test your code.
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!
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.