SL23W45: Difference between revisions

From ETM
Jump to navigation Jump to search
No edit summary
No edit summary
Line 25: Line 25:
***(wrong blocks red glow, out of bounds blocks gray blocks, possibly green for correct blocks)
***(wrong blocks red glow, out of bounds blocks gray blocks, possibly green for correct blocks)
***'''Needs to get informed on block changes in the given area, SchemaSnooper'''
***'''Needs to get informed on block changes in the given area, SchemaSnooper'''
***'''Green markers for correct placement could auto-disappear by using InterpStart and moving to Y=500 and Scale(0,0,0)'''
***
*
*

Revision as of 16:41, 16 November 2023

◄ SL23W44 | SL23W46 ►


  • ( Update room planning / cleanup for larger desk)
  • Big: Rebooting does not work if a debug-session is active and hangs for ~60 seconds.
    • Fixing HotSwapAgent to not prevent the shutdown when a debug-session is active
    • Add a shutdown-indicator to make HotSwapAgent skip redeploying classes on shutdown
  • Maybe create a Lombok+GC video from last stream
  • Marker Api
    • Very simple markers for chunkli, not knowing about the kadi markers
    • Implement an optimized ChunkSelection container that only uses a roaring bitset to minimize memory footprint and updates
      • KSelection as independent implementation from Chunklis ISession/Selection
      • Possibly add more information to a KSelection
      • BIG: Possibly make the KSelection immutable to allow integration into the desktop history state
    • First Version should be ChunkMarkers in specific as they have too many needed optimizations/interactions we want
      • Move up/down via display
      • Changed color based on plot-state
    • Second Version optimized area-markers or block-markers / SchemaMarker
      • Useful for blueprint manual building, one block-marker for each block that needs to be placed
      • Gives a todo-list of placements
    • BitsetChunkSelection / SchemaMarker / Schema
      • Schema is a state of a manual-building session of a blueprint
      • Has info about the blocks that need to be changed and spawns SchemaMarkers / glowing state for each block location representing the current state of the build process
      • (wrong blocks red glow, out of bounds blocks gray blocks, possibly green for correct blocks)
      • Needs to get informed on block changes in the given area, SchemaSnooper
      • Green markers for correct placement could auto-disappear by using InterpStart and moving to Y=500 and Scale(0,0,0)