From msg I can set the textHeight of a certain field to, say, 13, and from msg I always get "13" back when querying its textHeight. Great, eh?
In a large project, I have a test mouseDown handler in that field, and I placed this in a line in it:Which all of a sudden comes up empty.
This was in a utility where the user can click on any line in that field, and a tool would pop up at the clickV, pertinent to the line of interest. Today, LC has forgotten the textHeight of the field IN THE HANDLER, whereas if I go back to msg, any old time at an all, "13" comes up as expected.
The utility always appears at the top of the field, not at the line of interest, because the calculation that locates it is using empty as the value of the textHeight, and not 13. Great, eh?
Before I just assume it is, again, just me, and replace the textHeight reference with 13 (which means I cannot change the font size without modifying that explicit value) can anyone make sense of this?
Craig
In a large project, I have a test mouseDown handler in that field, and I placed this in a line in it:
CODE:
answer the textHeight of meThis was in a utility where the user can click on any line in that field, and a tool would pop up at the clickV, pertinent to the line of interest. Today, LC has forgotten the textHeight of the field IN THE HANDLER, whereas if I go back to msg, any old time at an all, "13" comes up as expected.
The utility always appears at the top of the field, not at the line of interest, because the calculation that locates it is using empty as the value of the textHeight, and not 13. Great, eh?
Before I just assume it is, again, just me, and replace the textHeight reference with 13 (which means I cannot change the font size without modifying that explicit value) can anyone make sense of this?
Craig
Statistics:Posted by dunbarx — Wed Oct 30, 2024 7:33 pm
