Lorenzo Gaifas
Lorenzo Gaifas
very odd! @Alems8, is that the whole output of `sys_info()`? It's missing the GL extension section. What is your hardware? (CPU and GPU) Also, can you try `examples/basics/visuals/markers.py`?
Wow... I don't know where to start debugging this xD Maybe changing backend? Could the `gl_Pointsize` have "zero" as maximum size on this specific hardware (similar to #2078)?
@Alems8 what do you mean "all I get is an empy bracket"? From what do you get that? Also, my only suggestion was about changing backend, is that what you...
> But please make a PR to update the Visual to pass `copy=False` to `np.array` (@brisvag what do you think?). Yup, agree! I would add an argument to `set_data(copy=False)` just...
If that's not enough, you can [update a buffer starting from an offset](https://github.com/vispy/vispy/blob/dd8140d6efccee75359059d7c0ed69fbad8059f1/vispy/gloo/buffer.py#L59). You could expose/use this method on your `LinearRegion.color_buf` and `LinearRegion.pos_buf` to only update what's needed. I'm not...
I think this is familiar... @petaflot, what happens if you simply multiply all the coordinates of the points by, say, 100 (making everything 100 times bigger)?
No worries, take your time! If scaling coordinates up fixes the visual bugs, it's almost certainly an issue I've seen before, and it likely comes from numerical precision in the...
> Could `divisor` be a keyword argument with a default of `0` for backwards compatibility? Yes, good point... I did make it a "silent" keyword in a couple of places,...
I moved the examples to `gloo` and `scene` (not sure if the latter makes sense?).