Forgot to add, try selecting comment text and you will notice how much more space selected area takes up then the text itself. This is what pd-l2ork takes into account when calculating whether something fits within the gop boundaries or not. HTH On Jul 3, 2013 1:35 PM, "Ivica Bukvic" ico@vt.edu wrote:
That is because tk renders them as such. In other words when text is written inside the canvas it is not just the text itself that takes up space but imagine a box around it as if you were to select text that actually within tk returns visible area required by the text itself. Finding out only the pixels assigned to text itself without having direct access to tk is extremely cumbersome if not impossible. This is also why comment when jam packed right against the edge of the graph on parent box is not visible because of this invisible selection area that is reserved for the text. On Jul 3, 2013 11:47 AM, "András Murányi" muranyia@gmail.com wrote:
On Wed, Jul 3, 2013 at 1:15 AM, Ivica Ico Bukvic ico@vt.edu wrote:
[...]
However, if the object appears within the GOP boundaries but is still not
visible in GOP window, then there may be some stale things I missed in the getrect call for hsl. In this case, please do file a bug report.
Best wishes,
Ico
I would. Where is the l2ork bug tracker? I see you don't use the tracker on github...
I have compiled the newest l2ork and things are almost perfect, if not perfect. My hsl and cnv still don't fit where they should but I've realized it's because of their labels. The labels are rendered seemingly inside the objects' boundaries, however I need to decrease the font size further to make them GOP. Please see the attached little example patch.
Thanks,
András