I've been asked to build a pretty simple application using Air, which runs on one PC but uses two monitors (laptop screen and second monitor / projector).
The idea is that there will be two distinct elements - a Controller window (laptop) and a Display window (second screen). For example, a dude will press a button on the laptop window, and it'll change the Display window - or information typed in the laptop will show on the second display. It sounds odd, but its for a game that someone wants to set up...........
I've been messing about a bit, and I've managed to default stuff to a second screen, but I'm not sure how to get it to show different content on each and how to define where the content lives.
is this possible, or is life just too short?
Related
We are currently checking if our app is compatible with the upcoming iPhone X and its new form factor and gestures.
We noticed a problem regarding the switch to home screen gesture where swiping up actually triggers the action on the buttons located at the bottom of the screen.
In our case, this is problematic, because our app is a remote controller for very high end amplifiers and the buttons located at the bottom of the screen are volume buttons..
See image:
Anyone here had to deal with this kind of issue lately?
I was thinking of some kind of event that could be triggered by the swipe up gesture and disabling the buttons maybe?
Thanks for your help.
So we finally decided to go for the safe area principle and stick our bottom bar to the bottom of the safe area as suggested by Apple.
It's a bit annoying as it adds a big empty space at the bottom of the screen but I guess every app having actions there will have the same problem (tab bar for example)
Here's the article I used:
https://useyourloaf.com/blog/safe-area-layout-guide/
If you found another solution, I would be happy to read about it.
Thanks.
Somewhere in the near future, an application I'm working on is going to its own pass to be stored in the user's passbook.
Since you cannot really test the passbook app from the watch in the simulator, and my watch will be arriving next month, I was hoping someone could shed some light..
I had a few questions about passbook for the apple watch..
Is it safe to assume the passes in passbook will automatically be
synced and added from the phone to the watch?
Are there any sort of visual guidelines when it comes to showing
passes on the apple watch? Does text automatically shrink? are things truncated? Are only certain fields appearing on the watch to conserve space?
Is it safe to assume if the user turns their wrist, the screen will
not shut off if a pass is currently being displayed?
Yes it automatically syncs.
Thus far I've noticed that the Pass is added to Apple Watch Passbook quite quickly after added in iPhone; although if you reorder the passes on the iPhone the order takes a little longer to sync on the Apple Watch view. (I haven't timed this under different scenarios but I'll test that and get back to you). Please note, I have >300 passes in Passbook so a 'typical consumer' may not experience the same.
Visual Guidelines.
The logo image remains at the top left of the Watch view of the Pass and automatically scales.
The strip or thumbnail image are removed from the Watch view. A background image (on an event ticket type) remains visible but is not scaled.
The header fields moves below the logo image (i.e. it is not to the right of the logo as it appears in the phone).
All other (text) fields appear on the watch view, but they are not side by side. The are presented in a 'list view' - separated by a fine line between each field. I have experienced some situations where the text length runs over one line (e.g. an email address i.e. no spaces between words) and it doesn't look so beautiful as the text does not resize to fit all on one line.
The pass automatically scales width-wise so it fits in the watch view but it is "longer" than the watch screen so you scroll the Pass up and down.
The pass length in the Watch app is dependent on the number of fields used in the Pass.
As you scroll to the QR code and tap on it, all other background colours and the 'close' link disappears and only the barcode is displayed. The square barcodes look significantly better. Of course redemption/scanning still works with the PDF417 barcode but it just doesn't look as nice in the watch view. It is presented in vertical format in the centre of the watch view, with black to the left and right of the PDF417 barcode.
Please note that there is no 'back view' on the apple watch pass. i.e. you cannot flip the pass to access the back of the pass as you can on the iPhone.
Screen shut off
The screen will not shut off only if the barcode has been selected (as described above). If you are just viewing the pass and have not selected the barcode the watch screen will shut off after time of no activity or if you turn your wrist.
If the barcode is selected, the barcode remains on the screen irrespective of wrist position and does not shut off over time.
Other - Lockscreen notifications / convenience.
Works the same as iPhone when in proximity to an associated GPS location or beacon or following a push update.
The pass can be accessed by tapping on the notification (i.e. no need to open the Passbook app on the watch) and can also be accessed by a swipe down to notifications. A 'small pass' is displayed in notifications. The 'small pass' is the same width as the watch face, and about half the height (same as other notifications). It consists of the logo image, inherits the background colour of the Pass, and includes the pass description field (when in proximity) or the updated field (when pushing an update).
I am trying to adapt an HTML based app for Chromecast and everything is working fine, except that the ":focus" is not taken into account in the CSS.
I am using it to display differently some items (basically the equivalent of the "selected item").
The focus is handled properly (calling ".focus()" on some DOM node works fine), just the display is not done properly.
I suspect this could be intentional as there is no keyboard and such for Chromecast. I could always rewrite the whole CSS to add a "focused" class on the element, but rewriting the whole thing just for Chromecast as it is already working on a number of platforms seems a bad idea.
Is there a way to activate the support for ":focus" in the CSS ?
Is there a work around ?
Best Regards
JN
The idea behind the chromecast is not to have a UI in the way that you are describing; the "control/navigation" is on the second screen and the consumption of content (playback of media, for example) is on TV. As an example, consider the Google Play Music. User picks up her mobile device, navigates through albums and such on her device till she finds the desired content. During this interaction, the TV screen doesn't try to show the navigation that is happening on her device and that makes sense since she is not even looking at the TV; in fact, it would have been pretty difficult to look at TV (assuming it was mirroring her mobile display) and navigate on her mobile device; user doesn't want to move her eyes from one to the other while she is searching through her content. Finally when she finds what she casts that to TV and can listen to that on her TV. It is the same behavior with the TV and Movies app, Netflix and Hulu+ as well and it is strongly recommended you follow the same pattern.
I build a web site in flex that some time take input. Will this website works on Touch Screen environment(KIOSK).My question is we have to make any change to handle input such as prompt on screen keyboard when input fields are get focused or it will manage my device and OS of system(KIOSK, Touch screen system) itself.
I'm unclear exactly what your question is. But, yes, Flex should work on touch screens and traditional screens with a mouse and keyboard.
It is likely that you'll need project modifications for each environment. The size of a button to accept a mouse click is going to be much smaller than what you need to accept a finger click, for example.
You can use a library project to share code between these two projects / interfaces.
I remember using Flex applications on touch screen monitors running Windows/Linux. These operating systems treat/converts touches as/into mouse actions and hence Flex apps doesn't know the difference.
Whether you'll be able to run it on a kiosk depends on the underlying OS. If the OS converts touches to mouse movements, then yeah, your app will run seamlessly.
How do I switch between the two screens on the Qt?
For example, I have a button - static text plus a toolbar. Now I will add it to a frame and set it as a central widget. It works well for one window. What if I move it to the next window? Then I need to show some other stuff like another button, some images etc... and what if I come back to the first view again?
How do I show my old widgets back?
I'm not sure I got your problem right but, you could have different scenarios :
You could simply use groupboxes... Some widgets in groupbox1, otherWidget in groupbox2, and you display the groupbox you want to use, hiding the others...
You could use stackedWidget, which simulates "pages" of widgets stacked on top of eachothers... more informations here : http://qt.nokia.com/doc/4.6/qstackedwidget.html.
You could use other way like using tabs : http://doc.trolltech.com/4.6/qtabwidget.html
Maybe this example would be useful to you : http://qt.nokia.com/doc/4.6/dialogs-configdialog.html
Hope it helps a bit !
I'd recommend checking out Animation/States example (should be in /qt/examples/animation/states/ subdirectory of your Qt installation). It shows how to combine state machine representing application logic with presentation layer and get cool animation effects for free (of course if you don't need eye candy, you can set widgets properties without any animation).