Technically I suppose this is not a Tiled "bug", but it sure is causing a bug in other software!
I am using PyTMX to read Tiled .tmx files into a Python program. I am seeing a crash in my Python program recently, like this one:
PyTMX is unable to interpret a value in the .tmx, which appears to be a "1.0.0" whereas it is expecting a valid float.
So I looked at the .tmx, and here is what I see:
Prior to the latest update, Tiled always produced a Map version value that was a valid float (stored in a string, but still a number here). In fact, looking back through my older saved .tmx files, that value was always "1.0". The change to "1.0.0", is causing interpretation issues downstream from Tiled, as that string gets converted to a float and then pukes.
Can this be changed so that a valid number is used here? Or other ideas to resolve? I just installed the most recent PyTMX and did not resolve it. Yes, maybe I can get those guys to change their parser code, but since the value written into Tiled really isn't a valid number in the first place, the most logical place to fix this is here IMHO.