This is an archived, read-only instance of the JaCaVi Trac. This site is no longer actively maintained. Registration and login have been disabled. Content is preserved for reference only.

Opened 18 years ago

Closed 18 years ago

#45 closed enhancement (fixed)

Implement checks for compatibility of track type with OS and technology

Reported by: Florian Roth Owned by: Florian Roth
Priority: major Milestone: MS1: First release (1.0.0)
Component: hal Version: pre-1.0
Keywords: Cc:

Description

Currently in my opinon we have the following relationships:
<p>
Digital Course -> Windows -> No HAL (only simulation)
That means we have to generate sensor data by our selfes.
<p>
Digital Course -> Linux -> lib42 HAL
<p>
Analogue Couse -> Windows -> Analogue and/or Bluerider
<p>
Analogue Couse -> Linux -> Analogue and/or Bluerider

Change History (9)

comment:1 Changed 18 years ago by Henrik Heimbuerger

Milestone: MS3: Input device and slot car track support → MS1: First usable version

Batch moved MS3 (input device/technology integration) to MS1 (first working version).

comment:2 Changed 18 years ago by Henrik Heimbuerger

Component: unspecified → hal
Type: task → enhancement

See also: MeetingProtokollFuenfundzwanzigsterAugust#zuTagesordnung, 5.

comment:3 Changed 18 years ago by Henrik Heimbuerger

Summary: Make sure that the compatibility mapping from course (digital / analogue) to HAL technology related to the underlaying os is given → Implement checks for compatibility of track type with OS and technology

Shortened summary. (Simply to make the reports prettier. ;) )

comment:4 Changed 18 years ago by Florian Roth

Owner: changed from somebody to Florian Roth
Status: new → accepted

comment:5 Changed 18 years ago by Florian Roth

I think include the os checks (linux/windows) etc. because there is a less possibility that someone configures a windows pc with serial interfaces (hardware cards) to connect to the 42 blackbox. If someone does, he/she must compile Clib42 and CsdLib? on windows by self.

comment:6 in reply to:  5 ; Changed 18 years ago by Florian Roth

Replying to froth:
I think wont include the os checks (linux/windows) etc. because there is a less possibility that someone configures a windows pc with serial interfaces (hardware cards) to connect to the 42 blackbox. If someone does, he/she must compile Clib42 and CsdLib? on windows by self.

comment:7 in reply to:  6 Changed 18 years ago by Florian Roth

I think I wont include the os checks (linux/windows) etc. because there is a less possibility that someone configures a windows pc with serial interfaces (hardware cards) to connect to the 42 blackbox. If someone does, he/she must compile Clib42 and CsdLib? on windows by self.

Forget the prev two comments

comment:8 Changed 18 years ago by SVN

New commit by froth (revision [282]):
[Related to ticket #45] added the track, connector combination validation in the RaceValidator?

The new Method in RaceValidator? will check players connector so that:

  • its not null
  • it has an valid uuid
  • the DriveConnectors? implmented interface to ensure that the current focused track could be combined with this connector

comment:9 Changed 18 years ago by Florian Roth

Resolution: → fixed
Status: accepted → closed
Note: See TracTickets for help on using tickets.