I am building an commercial app for fire-tv, and I need to change the soft keyboard. Add keys, resize the keyboard to fit screens etc. How can this be done on a fire-tv?
there are limited options for customizing the default on-screen keyboard.
When defining an EditText item, in XML you can use android:inputType="number" to switch to a numeric keyboard.
If you look at the UIWidgetsSample sample app in the Amazon Fire TV SDK there are some other options for customizing the on-screen keyboard (eg email) however for a large-scale customization you'll probably want to do as Hulu or Netflix have done and implement your own to have full control
Related
How to get notified for mouse wheel interaction for MacCatalyst and windows at MAUI platform.
Answer 1: Scrolling.
What do you want to do based on mouse wheel interaction? If you simply want to scroll, or know when scrolling has occurred, then you can rely on ScrollView, and other views that handle scrolling themselves. E.g. ScrollView.Scrolled event.
Answer 2: General use of mouse scroll wheel.
Input functionality for mouse or keyboard has not yet been implemented in MAUI. Nor has a specification been finalized.
Here is one mouse proposal.
You could add a comment to that proposal requesting that mouse wheel support be included.
However, this might not be in the first release of MAUI, as the current emphasis is on stabilizing the functionality that is needed on all platforms (including mobile), some of which don't have mice.
In case anyone is wondering "shouldn't this be specified in .net 6?" (And then MAUI would simply use it.)
There are interactions between what is happening on the display (views or windows) and how mouse/keyboard input should be handled - it makes sense to put that input in the same code base that is displaying to the screen - therefore MAUI is a good place for it.
Especially given that touch is part of MAUI.
Until then, the solution is to make a DependencyService on each platform, to refer to the platform's APIs that you need.
Surprisingly, I'm not finding one that anyone has done for mouse on Windows and Mac.
Other than "implicitly", since a mouse can be used similar to a touch device. And text can be typed on a keyboard. The point is that there is no API specific to functionality that only makes sense if you have a physical mouse (scroll wheel) or a physical keyboard (global keyboard hooks).
TBD I'll look into this further.
Basic approach would be to look at what WinUI 3 uses as input APIs.
On Windows Desktop app, forward to those input APIs. Write an adapter on other platforms (Mac, Linux).
I'll see if Uno Platform or Avalonia have taken this approach.
On the iPad, if a QML TextInput or TextEdit gains focus, the soft keyboard appears and the app content slides up as necessary so that both the text input field and the soft keyboard are visible.
On a Windows Surface Tablet, in tablet mode, Qt supports automatic showing of the soft keyboard, but the app content does not automatically slide up and the input field can be hidden behind the keyboard.
Is there a way to make the app content slide up automatically as it does on the iPad? Or is there a way to detect the presence and dimensions of the soft keyboard so that I can handle the slide up manually in code?
NB: the automatic showing of the soft keyboard on Windows in tablet mode was reported broken in this bug report (reported as early as Qt 5.3.2) but has been fixed as of Qt 5.11.2. Note also: these bugs affected Qt Widgets class QLineEdit also, and my issue may relate to that too but I have not tested it with Widgets.
I would like to create a preferences window like in the standard Mac OS X apps (Safari etc.). I have found resources like DBPrefsWindowController from back in 2008 that matches the Apple HIG.
Just wondering if there is a new way to accomplish this? I can't locate any standard windows in Interface Builder so I assume Apple doesn't provide those, nor can I locate a official Apple sample code for providing this standard UI.
Thank you
It seems DBPrefsWindowController is no longer available.
For now, I would recommend the up to date RHPreferences framework.
Available on GitHub. BSD Licensed.
It’s a simple and easy Preferences window controller with multiple tabs for your next Mac application.
It also provides:
Auto resizing between different sized tab views (With animation)
Custom NSToolbarItem support
Persistence of the last used tab
Support for placeholder NSToolbarItems (eg NSToolbarFlexibleSpaceItemIdentifier & NSToolbarShowFontsItemIdentifier)
Im about to start creating a custom onscreen keyboard for my WP7 app. An out of the box SIP will not work since they can't be customized or built from scratch with .NET.
Ideally the keyboard would activate like a SIP. Specifically, appear when the textbox receives focus. Docking to the bottom of the screen would be nice, too.
Any ideas where I could find samples of this?
Also, do you have any recommendations or lessons learned you could share?
I think you'll be making this sample ;)
The challenge with letting textbox take focus is likely going to be the built in SIP is going to appear. ReadOnly is an option, but you'll either lose or need to find a way to retain/mimic the cursor if that visual queue is important to you.
So we're re-designing a desktop application so that it's also usable with thye Touch Interface with Windows 7. We've consulted the UX guidelines.
For some part of the UI, there are toolbox icons that are disabled because of some arcane rules (the software communicates with a hardware device). We disable the actions that aren't applicable (because of some condition) and let the user hover the mouse on the tool icon to see the tooltip explanation on why that tool is disabled.
Since there is no "hover" for the touch interface (windows 7, iphone, ..) what is a better pattern/model for this?
Thanks!
Not an official solution but here's how I'll approach this until a better solution is available:
Make the item look disabled but still be clickable.
Add an overlay icon (of a question or similar) so it looks more than just disabled.
When clicked, display the message that would have been in the tooltip. Preferably in a non modal way and that doesn't require acknowledgement.
One option is to leave the control enabled and show a message when it is clicked to say why it won't do anything. However as stated in 'Disabled Menus Are Usable' this throws away valuable information for an experienced user (although this is less of an issue for icons than menus as there are usually less icons to go through than menus).
Another possibility is to provide a control like the click for help tools that were popular a few years ago. The user would first click on the 'why is this disabled' control, then click on the control that is disabled. This is however a rather clunky solution.
Another problem with toolbox icons on a touch interface is that the tooltip text is often essential as it is often impossible to convey complex/domain-specific actions with an icon. i would imagine many users on a touch only device will just use the menus instead as they can work out what they will do.