Current Work In Progress

2019-06-19: Added the index of the sphere to the datatype prot::ND_ImageData, -1 if not a sphere.

2019-06-10: the client will need to sent back to the server some information, after a navigation process. Initially, it has been assumed that this information would be only some images ("sphere differences"). See prot::ND_DiffInfo

To be able to send some more general information, the protocol will implement having the ability to sent also one or several arbitrary text files. Thus prot::ND_DiffInfo now has an additional member (_nbTextFiles) that holds the number of text files sent before/after the images (NOT IMPLEMENTED YET).

Bug:

2019-06-20: discovered, 2019-07-10: FIXED !

• Summary: internal Cancel event gets triggered

• steps:

  • run locally server and demo client 2
  • Enter on client the keyboard sequence c - i - n
  • What should happen: the initial cancel event should be ignored, and the two following steps should succeed ("initial contact" + "nav request")
  • what happens: initial Contact is ok but nav request fails because the previous cancel event gets triggered at the moment
    FIXED on 2019-07-10 !

  2019-07-12: new branch "3dim_sphere_coord", implementing 3 coordinates for sphere (x,y,z) Not in production !

  2019-07-12: branch 3dim_sphere_coord

  • changed size of reception buffer from 0x80000 (524 kB) to 0x400000 (4,19 MB), because some sphere images are larger than 2,2 MB
  • added transmission of z coordinate of sphere: This needed a lot of refactoring, new types (Location3d , Location2d)

2019-09-29: merged master into branch 3dim_sphere_coord

• integration of sphere index when transmitting
• fixed merge conflicts, build is ok (no tests at present)