Starting with Xojo 2023r1 you’ll find a new feature in Xojo’s Debugger panel that allows you to filter the objects and variables displayed, even between different project runs! This lets you stay focused on the more important objects and variables instead of scrolling through the list of all entries.
Comments closedTag: Debugging
Starting in Xojo 2022r2 you have the option to generate Program Database (PDB) files with your 64-bit Windows builds. If you’re unfamiliar with what PDB…
Comments closedYou may or may not be aware that running iOS projects in the Simulator does not allow you to check all of your app’s features. There are a few features which rely on hardware capabilities which the Simulator cannot emulate. This can make it hard to track down bugs, and the only recourse is console logging. Starting in Xojo 2022r1 it’s possible to run your apps right on a physical device connected by USB.
Comments closedYuck! It happens to everyone, from beginners to experienced developers: sometimes you’ll get stuck. Perhaps the code you’re working on just won’t do what you want or maybe you’re having trouble understanding code plucked from the internet. Talk to the duck. The rubber duck, that is. The term “rubber ducking” or “rubber duck debugging” is a software development technique where you explain the problem you are having to a rubber duck (or appropriate substitute). Often the act of explaining the problem to someone else, even if that someone is not real, can help you figure it out. It might be like inspiration struck.
Comments closedWhile 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 closedOften 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 closedA lot of times you’d think that single lines of code, aka “one-liners”, like
if j >= 145 condition then dosomething()
or
if condition then return
might not have any downsides. I would argue that they do.
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 closed