While we make the full transition of building the Xojo IDE for M1, you can continue to leverage debugging M1 apps while using the Intel based Xojo IDE on macOS.
Comments closedTag: Debugging
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.
Comments closedAt XDC 2019, I did a session called Avoiding Troubleshooting Troubles, which was essentially about ways to take advantage of the Xojo debugger. During the…
Comments closedHere are a couple tips you can use with computed properties.
Comments closedViruses 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.
Comments closedIn 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.
Comments closedXojo 2017 Release 1 includes support for running and debugging 64-bit apps right from the IDE for macOS and Linux. Windows support is noticeably absent. Why? The answer is a bit complicated but interesting.
Comments closedUsing 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.
Comments closedYou 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.
Comments closedSince 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.
Comments closed