Ticket #381 (closed todo: done)

Opened 2 years ago

Last modified 3 months ago

tests to pass: scopes/focus

Reported by: ichthyo Owned by: ichthyo
Priority: grave Milestone: 0integration
Component: lumieraProc Keywords: session
Cc: Blocked By: #346, #351, #370, #371, #372, #382, #402, #420, #455, #533, #662, #679
Blocking: #310, #401, #432

Description (last modified by ichthyo) (diff)

  • PlacementScope_test
  • QueryFocusStack_test
  • QueryFocus_test
  • ScopePath_test

Change History

comment:1 Changed 2 years ago by ichthyo

  • Blocked By 382 added

comment:2 Changed 2 years ago by ichthyo

  • Blocking 385 added

comment:3 Changed 2 years ago by ichthyo

  • Blocking 386 added

comment:4 Changed 2 years ago by ichthyo

  • Status changed from new to accepted
  • Blocked By 372 added

comment:5 Changed 2 years ago by ichthyo

  • Description modified (diff)
  • Blocked By 402 added

comment:6 Changed 2 years ago by ichthyo

  • Blocked By 420 added

comment:7 Changed 2 years ago by ichthyo

  • Blocking 432 added

comment:8 Changed 2 years ago by ichthyo

  • Description modified (diff)

comment:9 Changed 2 years ago by ichthyo

  • Blocked By 371 added

comment:10 Changed 2 years ago by ichthyo

  • Blocked By 455 added

(In #455) oops... consequences can be fatal, thats not just a minor issue. While normally the LUID-based Hash-ID doesn't allow to create zero LUIDs, there is a rather straight forward way to sneak in such a value from within PlacementRef -- which is exactly what we need. Is this a hack? It looks ok-ish to me, as it happens right from within implementation level and right there where it's needed (the default ctor of PlacementRef).

Thus I'm headed towards using a 0-LUID to mark invalid -- but this needs to be complemented by a dedicated check on each index insert

comment:11 Changed 2 years ago by ichthyo

  • Keywords session added; sesion removed

comment:12 Changed 2 years ago by ichthyo

  • Blocking 401 added; 385, 386 removed

PlacementIndex got an implementation facility and doesn't depend any longer on the scopes (it's rather the other way round)

comment:13 Changed 2 years ago by ichthyo

  • Blocked By 533 added

comment:14 Changed 2 years ago by ichthyo

  • Blocking

the basic query operations are working; next topic is to settle down on the generic query API used by the session, and then to combine it with the placement scopes (implemented but not yet tested)

comment:15 Changed 17 months ago by ichthyo

  • Blocked By 662 added

comment:16 Changed 16 months ago by ichthyo

  • Blocked By 346 added

comment:17 Changed 16 months ago by ichthyo

Heh.... the basic ScopePath_test runs green -- thats a big step ahead!

comment:18 Changed 16 months ago by ichthyo

QueryFocusStack_test runs green too

comment:19 Changed 16 months ago by ichthyo

  • Blocked By 679 added

comment:20 Changed 16 months ago by ichthyo

  • Status changed from accepted to closed
  • Resolution set to done

augmented with diagnostic output, all these tests pass now

comment:21 Changed 3 months ago by ichthyo

  • Blocking 401 added

comment:22 Changed 3 months ago by ichthyo

  • Blocking 401 removed
Note: See TracTickets for help on using tickets.