getSystem | webshell下提权执行命令 Reference https

In Akka Classic, you would have something like

You can you do this on layout by wrapping the ConstraintLayout in another one that has a height that matches the screen height.

Then add the below constraints to the inner ConstraintLayout to get a max height of 80% of the total screen height. This requires to have a height that match constraints

Since no-one provided any answer how to avoid context, the only way is to use context or get the ID of the STRING object and send back.

Option #1:

Actually the problem was related to phone's language, if the language is rtl the problem shows, as the layout reversed, so the startMargin keep applying it self to the edge (where the image initially generated in right), and I fixed the problem by setting the layout direction to ltr by using:

As @Micheal pointed out, I used Resources.getSystem() to get strings from resources. Instead I should have used a context to call getResources(). A simple fix should look like this.

For inner classes the syntax becomes:

The DisplayMetrics class includes all the information you need:

• widthPixels
• xdpi

And

• heightPixels
• ydpi

These second values correspond to the number of pixels per inch for the physical screen, so you can compute e.g. the width in inches like this:

Try to override onMeasure()method and call setMeasuredDimension() with the measured width, and adding the a new value to the vertical/horizontal padding.

Ok, here's your problem. You want a wheel with 00 and 30 on it, and you want to be able to infinitely scroll it, so it ticks over from 30 to 00 and increments the hour wheel each time, right? Which is basically how the TimePicker works by default.

The issue is this, from NumberPicker:

Note: If the number of items, i.e. the range ( getMaxValue() - getMinValue()) is less than the number of items shown on the selector wheel, the selector wheel will not wrap.

the max - min thing is an extremely awkward way of expressing this (the number of items is actually that + 1) - but basically the spinner shows three items on-screen at a time, and you need to have more than three items (so at least one is off-screen) for wrapping to work. That's why is works for your other intervals (15 mins gives you four items, so that wraps)

Unfortunately I don't think there's a lot you can do about it - the lack of wrapping is hardcoded behaviour in NumberPicker. You could fake it by having four items, 00, 30, 00, 30 but internally that's still values 0 to 3, one rotation of the wheel, not two. And the TimePicker uses those values, comparing to minValue and maxValue to check when the wheel has wrapped and the hour needs to automatically change.

The listener that handles this (in TimePickerSpinnerDelegate) can't be read, so you can't wrap it in a listener that pretends it's going 0 1 0 1 instead. The listener also refers to a bunch of internal private variables and methods, so you can't just copy it into your own code and make the tweaks. You'd have to reimplement the whole widget and its related classes by the looks of things

If it works for you, you could just throw two NumberPickers together and remake it yourself. You'll lose things like the AM/PM functionality, probably accessibility, it depends if you care or not. This basically works: