On Mar 12, 2014, at 11:01 AM, Fraser Gordon wrote:
> Hi all,
>
> Due to the many responses we received to our question about adding new chunk
> types to the LiveCode engine, I thought it might be useful to ask you about
> another potential change coming in LiveCode 7.0: how fields should hand
On 3/12/14, 12:01 PM, Fraser Gordon wrote:
Question 1: should the text alignment options be expanded to include
"start" and "end"? (Start means right for RTL and left for LTR while
end is the opposite)
That could work. It allows a degree of flexibility. The default "start"
should be "left" if
Fraser,
Would it make sense to add a textDirection or textFlow property to
fields, to indicate the native direction of the text? In my simplistic
way of seeing things this would make for less confusion. Then you can
have right-aligned LTR text (e.g. a column of numbers) and left-aligned
RTL t
On 12/03/14 19:49, Paul Dupuis wrote:
Add start and end - that way programmers can be explicit in what they want.
Given a start and end alignment, I would suggest left and right always
be left and right explicitly rather than dependent upon the whether the
script itself is RTL or LTR. This prese
Add start and end - that way programmers can be explicit in what they want.
Given a start and end alignment, I would suggest left and right always
be left and right explicitly rather than dependent upon the whether the
script itself is RTL or LTR. This preserves a level of backwards
compatability
Hi all,
Due to the many responses we received to our question about adding new chunk
types to the LiveCode engine, I thought it might be useful to ask you about
another potential change coming in LiveCode 7.0: how fields should handle
bi-directional text.
Currently, fields can be aligned to th
