Bug regression

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Bug regression

** Clarence P Martin ** via use-livecode
I found a bug that was squashed in 8.1.0dp3 has re-appeared. What's  
the proper way to report this? I found the original thread (marked  
FIXED) and made a comment, but not sure that anyone revisits those.

http://quality.livecode.com/show_bug.cgi?id=17852

--Andrew Bell


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Bug regression

** Clarence P Martin ** via use-livecode
Hi Andrew,

In such cases, I would suggest to file a new bug report (and probably
mention the number of the old bug that reappeared).

However, in this specific case, what happens is a bit more complicated.
What you see is a result of some changes we have done in the segmented
control widget in LC 9.0 DP-2:

1. In LC 9.0 DP-2 the segmented control widget has been improved. One of
the changes is that you can now have no hilited items at all.

You can verify that by trying the following test, in 8.1.6 and 9.0 DP-8:

- Create a stack
- Drag a segmented control widget onto the card
- Switch to run mode
- Click twice on "Label 1"

RESULTS:
- In LC 8.1.6, the second click does not un-hilite "Label 1"
- in LC 9.0 DP-8, it does.

IMO the correct behavior is the one in 9.0 DP-8, since there might be cases
where you don't want any hilitedItem at all.

2. Now regarding the textAlign issue in the Property Inspector, when you
select multiple objects that have a different value for a property X, the
value of the property X in the property inspector is set to empty (meaning
that the multiple objects don't have the same value for property X) and the
respective property field is greyed out. But since in this case you cannot
have the textAlign being empty, the "default" value (e.g "item1" -> left)
is re-hilited.

This issue is tracked in this report:

http://quality.livecode.com/show_bug.cgi?id=19441

Best regards,
Panos
--








On Thu, Aug 10, 2017 at 4:06 PM, Andrew Bell via use-livecode <
[hidden email]> wrote:

> I found a bug that was squashed in 8.1.0dp3 has re-appeared. What's the
> proper way to report this? I found the original thread (marked FIXED) and
> made a comment, but not sure that anyone revisits those.
>
> http://quality.livecode.com/show_bug.cgi?id=17852
>
> --Andrew Bell
>
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Loading...