On Fri, Feb 12, 2016 at 9:51 PM, Davide Andreoli <[email protected]> wrote: > 2016-02-12 21:30 GMT+01:00 Shilpa Singh <[email protected]>: >> http://git.enlightenment.org/core/elementary.git/commit/?id=a3e66305d7601fa4a62629ec2ceb29a1af274915 >> >> commit a3e66305d7601fa4a62629ec2ceb29a1af274915 >> Author: Shilpa Singh <[email protected]> >> Date: Fri Feb 12 20:38:36 2016 +0100 >> >> spinner: add min, max filter >> >> Summary: >> In spinner's entry allow numbers only with in min/max range >> Signed-off-by: Shilpa Singh <[email protected]> >> >> @feature >> >> Test Plan: >> 1. Set min/max value to spinner >> 2. Enter numbers beyond min/max value >> > > Is there a reason why this is only enabled in mobile profile? I cannot > either see why this is configurable at all, seems to me that this check > should be always on... no?
Yes, we were not sure to not break current application that would have hacked spinner in unexpected way. Ideally I agree it shouldn't be optional, but as I wasn't convinced this is a first step. If you think it is safe to turn on always, we should go ahead then. -- Cedric BAIL ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
