First, thanks everyone for your replies!
Are they?? I'll check that in a minute.
Ha! Sorry to hurt your brain! I was trying to debug something that was blowing up, and wanted a quick & dirty way to see the error message without having to look up the codes. Some of the errors had a range (e.g., 502 to 518 = Out of memory) and I was feeling lazy, so I generated that code by copying the tables from the QB64PE error codes page into Excel, then using a SUBSTITUTE formula to fill in the values, and the fastest path was to simply do a "one size fits all" template, even where there was only one value.
![[Image: qb64pe-lazy-error-message-code-generator.png]](https://i.ibb.co/XZLB3zC8/qb64pe-lazy-error-message-code-generator.png)
I agree. This wasn't for a user, this was me grasping for straws trying to debug some puzzling errors. At this point I don't remember what it was, but it eventually got fixed.
I think that is probably likely... Where is this happening? I basically copied this code from all over the place and it seemed to work in the past... You know that saying, if it ain't broke? I don't think that covers the case where it wasn't broke but then you broke it!
Anyway, I'll check the data types and the parameter order. Thanks again y'all...
(10-21-2025, 02:53 PM)SMcNeill Wrote: Isn't your coordinates reversed?
Sub PlotPoint (Y As Integer, X As Integer, S As String, MyArray() As String * 1)
Sub PlotSemiCircle (XC As Integer, YC As Integer, R As Integer, Q As Integer, S As String, MyArray() As String * 1)
One is X/Y, then the other is Y/X, and somewhere along the brain my mind is bugging out. LOL
Are they?? I'll check that in a minute.
(10-21-2025, 03:02 PM)SMcNeill Wrote: And can I ask about these statements -- this is just making my OCD twitch, and I didn't even know I *had* OCD:
If Err >= 1 And Err <= 1 Then
...
My brain is hurting. This code is twitching my eyebrows. LOL!!
Ha! Sorry to hurt your brain! I was trying to debug something that was blowing up, and wanted a quick & dirty way to see the error message without having to look up the codes. Some of the errors had a range (e.g., 502 to 518 = Out of memory) and I was feeling lazy, so I generated that code by copying the tables from the QB64PE error codes page into Excel, then using a SUBSTITUTE formula to fill in the values, and the fastest path was to simply do a "one size fits all" template, even where there was only one value.
(10-21-2025, 05:46 PM)bplus Wrote: OMG error handling galore!
I learned early on there is NO WAY to anticipate all the fool errors that could happen and attempting to code for even a likely majority was a boring nightmare.
The solution is simple, make no errors and inform users as best you can what info you are looking to get and how it will be used and allow for some intelligence from your user.
I agree. This wasn't for a user, this was me grasping for straws trying to debug some puzzling errors. At this point I don't remember what it was, but it eventually got fixed.
(10-21-2025, 08:58 PM)Petr Wrote: I assume the error is in the wrong use of data types. Are you really using the INTEGER data type for decimal numbers?
I think that is probably likely... Where is this happening? I basically copied this code from all over the place and it seemed to work in the past... You know that saying, if it ain't broke? I don't think that covers the case where it wasn't broke but then you broke it!
Anyway, I'll check the data types and the parameter order. Thanks again y'all...