why does rubric checks for maxVal at first instance?
> On 29 Mar 2017, at 14:07, Andrei Chis <[email protected]> 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?
>
> Cheers,
> Andrei
