Sat Feb 21, 2015 2:48 pm by BitTwiddler
The lucky 0.13 version of TrackEdit is out.
Changes
- Can now create a new track. When saved, ti will save a copy of the rendered line as the image. You for the moment have to replace it yourself. (I'll add an UI later to allow you to select one to replace it).
- Added the ability to flip all the cambers on the track, just in case you used an older version and got them messed up because of
- Added a projection line, so you know where your track will end up. This is not a track segment, it is just a guide tool.
- The program now creates a "trackedit.cfg" file. In the file you can configure the colors the program uses (i'll add an UI to do let you do that later).
- Fixed a bug where the launcher executable didn't work in paths with a space in them (whoops! I feel dumb!)
- Fixed upper bounds on the split time, the new upper limit is 1000 km. IF you have a track longer than 1000 km... well let me know, and i'll put some effort into removing the cap entirely.
- Fixed the camber helper image.
- Fixed a bug that kept helper images from sometimes updating.
A rough to list in no particular order of what I need to do next.
- Add options dialog (for colors and whatever else)
- Split some of my view/controller stuff into separate files
- Zoom feature. Even just stretching it ugly like (NN) is a bit involved, since I have to resize and recenter the canvas and track zoom level and so on.
- Home Grow an elevation graph, so I can allow selecting and zooming in on that as well (not the same kind of zoom as the image). Maybe just make it wider after a certain number of segments to keep it from becoming useless.
I can maybe allow a naive version of undo, which just keeps a copy of the entire internal state. But this is both lazy (thus possible) and a massive memory hog. Let me know if undo is a really big deal for you. So to have 1 undo state, the memory usage would double. To have 5 undo's the programs size would increase by 6 times, and so on.
Preserving raw elevation rather then the ratio is a bit problematic. Since if you scale a 100m high segment from 200m to only say 20m, well i'm not mathematician, but 20m < 100m. Which isn't happening. But even in the case of reducing a 100 m high segment from 200m to 100m means that segment turns from a 45 degree slope into a 90 degree wall, which isn't supported by the track format (it would be infinite percent tall). If you can think of a nice way to handle this so that these kind of problems don't occur, please let me know, and i'll consider implementing it.