Printing in LC 7.0.3

Terence Heaford t.heaford at icloud.com
Fri Mar 6 03:03:00 EST 2015


> On 5 Mar 2015, at 23:12, Richard Gaskin <ambassador at fourthworld.com> wrote:
> 
> For those interested in this text alignment issue in tab controls on OS X, here are the two relevant bug reports:
> 
> Bug 6206 - Tab Panels in Mac OS X have incorrect default text vertical position
> <http://quality.runrev.com/show_bug.cgi?id=6206 <http://quality.runrev.com/show_bug.cgi?id=6206>>
> 
> Bug 7962 - Tabs not centered horizontally in tab button
> <http://quality.runrev.com/show_bug.cgi?id=7962 <http://quality.runrev.com/show_bug.cgi?id=7962>>


Yes but Bug 6206 was reported on the 24 March 2008 - Thats just coming up to 7 Years.
and
Bug 7962 was reported on 15 April 2009 - Thats 1 month off 6 Years.

If someone considering moving to LC saw that User Interface defects can take this long to sort out then why should they.

I suppose by the same logic Bernd’s request for help via. Bug 14238 - backgroundpattern of a field out of sync if formattedHeight > roughly 32768 may also never get addressed and if someone had committed to modTableField they could well be up the proverbial creek without a paddle.

When the status of a Bug is CONFIRMED what is the decision process with regard to.

1. Whether or not it will be actioned.
2. When it will be allocated to an engineer.
3. When it will be actioned by.
4. If the decision is taken not to action, is the reporter of the Bug informed?
5. If the decision is taken not to action is the CONFIRMED status set to something else?
6. If someone has reported a Bug and no action is taken in a time scale what happens.
7. Does anyone actually look at Bug reports as old as those above?


All the best

Terry





More information about the use-livecode mailing list