orenshatz

Already covered by my multi-channel loader design proposal in the slack loader channel. But it would be funny if small parts of it would be issued as enhancements, and eventually...

Hi Stephan. Yes, it would be nice. The problem is, at the moment knossos users access data mostly remotely, whereas the data actually loaded in knossos is only a small...

I guess that's the way to go, yes, except acquiring remote data on per-file basis is usually extremely inefficient. At least for raw data, which would probably be left unchanged...

While this feature should foremost handle keyboard and mouse, the named hash approach should also allow responding to knossos events (that are currently hard-coded, but custom events may be added...

If it happens regularly use a screen video capture so we know what has been done beforehand. Never happened to me so far. Possibly a hardware issue or OS specific?

Possibly two different scenarios? Fabi's case looks like a memory corruption, or else there wouldn't be so many critical/assertions. While your case seems more transient (or do you also see...

I assume the log is symptomatic to the deeper issue Fabi had, e.g. corruption, which might account for the other symptomatic update arrest. Unless "no slot" is still quite common...

AFAIK we should never miss a slot (wrongly stated Critical, this is in fact a simple assertion).

Or it means that the unbuggy logic works on corrupt data. Again, unless this assertion is quite common, even in the absence of other problems.

What is meant by slice between cubes? I don't see any cost-effective trade off where the desired result is a 30 pixels long line of which a 5 pixels stretch...