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:
Comments closedCategory: Tips
sort code tips and tricks
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):
Comments closedUPDATE 12/2024
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.
If you are on Windows, you may also be interested in Avoiding False-Positive Virus Detection in Windows Apps
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.
Consider the following code:
dim i64 as Int64 = 1234567 dim i32 as int32 = 7654321 i32 = Int32(i64) // cast i64 = Int64(i32) // cast i32 = Ctype(i64, Int32) // convert i64 = Ctype(i32, Int64) // convert
It all seems reasonable enough. Not useful, but seems reasonable. Only one problem. It won’t compile. Why not? The two casts to int32 and int64 will fail. Now why is that?
Comments closedOperator_Lookup and ParamArray are two language features that have been in Xojo for a while now, but most probably don’t know why they were originally added. The need grew out from having to support COM on Windows.
With Xojo 2015 Release 2, most of the new Xojo framework is available for all project types. This includes Xojo.Net.HTTPSocket, which adds support for HTTP 1.1.
Comments closedMuch of the new Xojo framework is available for all project types staring with Xojo 2015r2. The Data namespace includes two methods for dealing with JSON data: GenerateJSON and ParseJSON. This is how they are used in comparison to JSONItem in the old “Classic” framework.
Comments closedWith Xojo 2015 Release 2, much of the new Xojo framework is now available for use in all project types. Because the new Xojo framework uses namespaces, you might want to take advantage of the Using command to help make your code easier to read and write.
But first, a brief aside about namespaces. The Xojo framework uses namespaces to provide better grouping of related features and to allow for classes with the same name to co-exist (Xojo.Core.Dictionary and Dictionary, for example). In fact, you can mix classic framework code and Xojo framework code together in the same method!
Comments closedWayne Golding has been a Xojo developer since 2005. He operates an IT Company Axis Direct Ltd www.axisdirect.nz which primarily develops applications using Xojo that integrate with Xero www.xero.com. Wayneâs hobby is robotics where he uses Xojo to build applications for his Pi2 often implementing IoT for remote control.
When receiving data from remote sources there are two options available, one option is where the source will send a packet size followed by the data, the other is where the packet is terminated. Today we’re going to look at the terminated version.
Comments closedBut it said DataAvailable…where is all my data?
I’ve seen this a few times and have made the mistake once or twice myself. You write some code with TCP sockets and rely on the DataAvailable event as if it means “all your data is here”.
But it’s not. So the code you wrote that parses the data into its components keels over because you only have part of what you were expecting to have. And so you ask: “Why isn’t all my data here”?
Comments closed