March 29, 2017
2:03 p.m.
Hi Andrei,
On Mar 29, 2017, at 5:07 AM, Andrei Chis <chisvasileandrei@gmail.com> wrote:
Hi,
Right now rubric relies on 'SmallInteger maxVal' to set the drawing bounds when a size is not set for the editor. This has some side-effects, like the text in Spotter not appearing on 64 bit given that some drawing methods from the graphical backend seem to expect 32 bit ranges. We can fix this by introducing #maxVal32 or maybe there could be some range checks in the canvas. Comments?
Why not introduce a class variable or a Rubric method that answers a constant? It could be the same as 2^30-1 or something smaller. What is the likely maximum extent of a Rubric drawing surface over the next ten years?
Cheers, Andrei