Cosmetic Bug MAXIDE (Mac)
Archives Forums/BlitzMax Bug Reports/Cosmetic Bug MAXIDE (Mac)
| ||
Take a look at this screenshot You can see all the "._" files MacOS X (or rather the Finder) creates by itself (unfortunately) in the help tree. I did code a tool once to remove them all automatically (not just from BMax, but from all my devices in general) and no damage was caused in the process. It's not a major bug, but it looks a bit messy. |
| ||
Can't confirm the exact one above, but can confirm that recompiling MaxIDE CE gives weird results in the code view: I've got a type split now into two types! with the second one having a title that comes from a string? Sorta similar... |
| ||
I've trashed the CE long ago, because I had one crash after another and I lost tons of source code in the process (and saving every 2 seconds is not the best way to go). This bug is not just MaxIDE itself actually. I see the documentation builder also respond to these "._" files the finder creates. It's not a huge thing, since you can safely remove all these files and BlitzMax will run perfectly, but it just looks a bit messy (and unprofessional). |