On iOS Safari, the time picker sliders from the sap.m namespace behave unexpectedly. When you select a value at a slider, you have to tap on a different one in order to "really select" the previous value. This even applies to the example in the Demo Kit.
E.g. if you want to select 9:41am, I would usually select 9 at the hours slider, tap on the minutes slider in order to confirm the hour selection and change the minutes to 41. Then I would (w/o tapping a different slider) press the OK button to close the dialog and display the output on the page. On iOS Safari, however, you have to tap another slider (e.g. the am/pm one) after the last selection in order to confirm the minutes selection. Otherwise it will apparently not detect that the minutes slider has been changed and only update the hours on the page.
If you have any idea on how to fix this, I would love to hear your answer :)
Related
I'm trying to build a timer app on MacOS that would show the remaining time in the status bar.
Wondering if it's possible to show multiple buttons there at once? E.g. show play/pause button, reset button and the time right in the status bar.
Or are there any hacks possible, like make it a single button with 2 icons next to each other, and check the click position to see which "button" got the click?
I know I can put the extra buttons in a popover, but I'm new to MacOS dev and trying to understand the limits. Thanks!
In Flutter, when using showDatePicker, why is the pressed date value not immediately accepted (without having to press OK)?
For example, if the widget initially opens at September 10th, 2019 and I want to select October 5th, 2019, I would expect switch the month to October and press 5 from the calendar display which would then automatically accept the date as October 5th, 2019 without having to press the OK button.
Is there a way to avoid needing to press the OK button?
This doesn't really sound like a code issue, but I'll answer anyway.
The reasoning you have to press OK is mainly to optimize the user experience. Essentially, some people just have either bigger fingers or smaller screens, so they may bump the wrong date by mistake, and some may not even realize it if the dialog disappears after they select the date. Adding the OK button prevents users from running into this problem.
I'm looking for help in creating an AutoHotKey script so that when I click the left button of my mouse and hold it down for 5 seconds, it triggers a "click-and-hold" action until I click it again to release. If it's not possible by holding it down 5 seconds, then perhaps by clicking it 3 times in a row?
I would say either way is possible. Have you looked into
KeyWait at
https://www.autohotkey.com/docs/commands/KeyWait.htm
and/or
GetKeyState at
https://www.autohotkey.com/docs/commands/GetKeyState.htm
and the examples in there yet?
In the first scenario, after detecting mouse down, you check again 5 seconds later to see if it is still down, or immediately return upon a mouse up (before the 5 secs are elapsed).
In the second scenario, you do multiple keywaits (the example does a double click, but just add to it one more level to detect three clicks).
Btw, if you show us your code so far, we can help with specific issues you may have getting it to work since it is a bit tricky.
Hth,
For the time being, this is a Material-UI question.
I have a situation where the tab key ceases to move the text cursor between TextFields. At the moment, I have no idea where in my code this is happening, and I am hoping someone can point me in the right direction so I can start looking.
Here’s the setup:
A mouse click causes a Dialog to be displayed. The Dialog has
several TextFields as well as 2 FlatButtons, “cancel & “submit”
At this state, tabbing between fields works as expected.
If I hit the “cancel” button, an event is fired which updates state (including the display of the Dialog) and the Dialog is closed. I can repeat the process from the top with no issues.
If I hit the “submit” button, an event is fired which does some async stuff (using rxjs epics).
On success, the epic fires an event which updates the state (including the display of the Dialog)
If I now try to repeat the process from the top, the tab key does not respond.
I am in the process of migrating to v1, and checked some of the v0.* components – they have the same problem – I don’t recall that being an issue before… Possible conflict between the two versions of the library?
Figured it out. Yes, there is a conflict between the v0.20 and v1.0 of the Dialog component. At least when you have one opening on top of another. Having changed all Dialogs to v1.0, the problem disappeared.
By the way, its not that the tab key wasn't responding - it was responding in the lower Dialog component and not in the top (latest to be created) one. This problem disappeared once the same version was used for both.
I have experience in Android and currently started to learn iOS. I created a mechanism to Pick data in an Android App. When I click on Date button, a DatePicker pops up:
As you see It has Cancel and Set button.
My question is about my iphone App. I want to have the same mechanism. When I click on the button, Date picker pops up (that can have Set and cancel button like Android Date picker). How can I do that? I'm not sure that it is a good way in iPhone, Can you help me if we can design a better mechanism?
Here's a UX comparison between Android and iOS standard widgets, with links to the documentation on the relevant Apple / Android websites. It's a nice way to get started learning all the technical terms.
http://kintek.com.au/blog/portkit-ux-metaphor-equivalents-for-ios-6-and-android-4/
Hopefully that gets you started.
Apple has a sample project that demonstrates this. You'll have to adapt it slightly: instead of showing/hiding the date picker itself, you'll want to show/hide a view containing a date picker and a dismissal button.
It's called DateCell.
Basically, it treats the date picker as if it were the keyboard for a cell containing the date. You'll need to manage hiding it when the user enters a text field (and thus, needs the real keyboard) and scrolling to keep the date row in view, but all the bits you need are in this project one way or the other.
One way to do it would be add a custom buttons to the same view containing date picker and then pop it up when the users wants. Instead of using the date picker delegate use the buttons action to get the date picker value.