Opened 18 years ago
Closed 18 years ago
#19 closed task (fixed)
Acquire bitmaps of track sections and cars
| Reported by: | Henrik Heimbuerger | Owned by: | Stefanos Papadopoulos |
|---|---|---|---|
| Priority: | major | Milestone: | MS1: First release (1.0.0) |
| Component: | track | Version: | pre-1.0 |
| Keywords: | bitmaps | Cc: |
Description
We need bitmaps of all the track sections (both for the analogue as well as the digital slot car tracks) for the visualisation part. Additionally, bitmaps of cars to visualise the current positions.
We could make photos of the actual sections and cars using a digital camera. However, they would all have to be in the same scale (probably requiring some kind of tripod to do that properly). However, this would require quite some manual editing to make them look professional.
In this case, we need them in the highest quality possible and ideally with lossless compression (i.e. no JPEG).
Alternatively, there might be sources of already digital images online. On the other hand, most of these are probably copyrighted.
Comments welcome...
Change History (19)
comment:1 Changed 18 years ago by
comment:2 Changed 18 years ago by
comment:3 Changed 18 years ago by
| Owner: | changed from somebody to Stefanos Papadopoulos |
|---|---|
| Status: | new → assigned |
comment:4 Changed 18 years ago by
| Status: | assigned → accepted |
|---|
comment:5 Changed 18 years ago by
New commit by hheimbuerger (revision [116]):
[Partial fix for ticket #6, related to ticket #19] The track designer now retrieves the available tiles from the tileset repository.
The track designer now retrieves the available tiles from the tileset repository. It's currently using only the debug tileset, because the class doesn't know which tileset the user wants yet.
The preview images are loaded as SWT images, separately from the Java2D images stored in the tileset repository. It could be discussed whether it would make more sense to convert the Java2D images to SWT images (which technically simple), as the Java2D are already in memory anyway.
Some modifications were necessary to make this possible:
- Tiles now have a display name.
- The Tile now provides getters for the display name and the filename.
- The TilesetRepository now stores the tiles of a specific tileset in a SortedMap? instead of a Map, so the ordering used in the tiles.xml will also be used in the track designer.
NOTE: The application will crash if no display name of a tile (attribute name on the tiles element) is defined in the tiles.xml.
comment:6 Changed 18 years ago by
comment:7 Changed 18 years ago by
comment:8 Changed 18 years ago by
New commit by hheimbuerger (revision [139]):
[Fix and cleanup for ticket #19] Restored the debug tiles and updated the tile definition file to the latest format.
Restored the debug tiles that were accidentally removed in [135]. Also added them back to the tiles.xml.
Initial tiles are now mandatory, so an initial tile was added to the digital tileset (currently using the same image as the normal straight). The demo track was extended by a reference to this initial tile.
comment:9 Changed 18 years ago by
New commit by hheimbuerger (revision [140]):
[Partial fix for ticket #25, related to ticket #19] Added support for specifying the car slots in the tile definition and added debug code for displaying the slots and moving objects around on them.
The tiles.xml now requires two slots to be specified for each tile. A slot consists of one or more parts of various types. The slot parts are used in the order specified.
So far, two different slot part types have been implemented. The element <line> can be used to define a slot part that goes straight from a point A to a point B. The element <quad-bezier> can be used to define a quadratic B?\195?\169zier curve.
The length attribute defines how many 'steps' are used to traverse a slot part and need to be modeled very accurately after the real track. It is also used to assign each position on the track a unique scalar value, thereby making locations very simple to store and modify.
Purely for demonstration purposes, the track widget currently draws the slots (in blue and yellow) and moves carets along them (in red). Determining the direction of an object on a slot has not yet been implemented.
NOTE 1: The application currently crashes when it is terminated while the track widget is still open. This is probably because the widget's dispose handler isn't invoked before the widget is disposed. I haven't found a way to fix that yet.
NOTE 2: The CPU usage is still rather high, I'm sure optimisations are possible.
comment:10 Changed 18 years ago by
comment:11 Changed 18 years ago by
comment:12 Changed 18 years ago by
comment:13 Changed 18 years ago by
comment:14 Changed 18 years ago by
| Milestone: | MS2: Track editor available → MS1: First usable version |
|---|
Batch moved all tickets from MS2 (track editor) to MS1 (first working version).
comment:15 Changed 18 years ago by
| Component: | project → track |
|---|
comment:16 Changed 18 years ago by
comment:17 Changed 18 years ago by
comment:18 Changed 18 years ago by
comment:19 Changed 18 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |

New commit by froth (revision [111]):
[Related to ticket #19] added the digital original carrera parts