Quicktime X - How to hide mouse during screen capture? - ios-simulator

I am attempting to record an app demo on the simulator, and want to use the Quicktime screen capture feature. However, I would like to hide the mouse during the capture.
Is this possible?
Doesn't seem to be a built in feature, so I am assuming I need to use some sort of plugin or hack.
Any suggestions?

QuickTime itself does not seem to offer this functionality therefore you have to resort to some other means to hide the cursor. On OSX there are some tools that allow this.
Cursourcerer is the first that springs to mind. However, as this really hides the cursor, it might not be ideal as you yourself will not be able to see what you are doing.
However, if you do not need to use QuickTime per se, it seems there are commercial screen recording solutions allowing this sort of thing such as Screenflow. I am not affiliated but the price seems reasonable and there is a demonstration of desired behavior here.

You don't record your app in your computer, but directly on your iPad or iPhone, connected to your Mac with a lightning cable. Then in Quicktime you select the "New movie recording" option (instead of "New screen recording"), then you will be able to select your iPad/iPhone as the "camera" and start recording your app running in your iOS device without any mouse pointer.

https://obsproject.com/
OBS can record your app window, and it ignores the cursor on the window.
Useful even if you are not a youtuber.

Cursorcerer for 10.14+ ⇨
http://doomlaser.com/cursorcerer-hide-your-cursor-at-will/
MouseHider.app for 10.13 and earlier ⇨ https://apps.apple.com/us/app/mouse-hider/id894419721?mt=12
I use option+command+k (⌥+⌘+k) to show / hide. It works globally.
It's also useful to hide the mouse cursor when you do the control-scroll zoom trick to focus in on a video.

Related

How do I test the accessibility of my Firefox extension's toolbar button (and attached popup)?

I'm writing a Firefox (web)extension. I have a browser_action in my manifest.json, with a default_popup. I want my extension to be accessible by all users, including those with vision impairment.
So I'd like to, as I change and develop things, test what it's like to (for example) interact with this feature, using only the keyboard. How do I do this? How do I focus and thus "click" the toolbar button, without a mouse?
Ideally, without actually running special screen reader software every time.
So I'd like to, as I change and develop things, test what it's like to
(for example) interact with this feature, using only the keyboard. How
do I do this? How do I focus and thus "click" the toolbar button,
without a mouse?
You can use commands to set a keyboard shortcut.
_execute_browser_action: works like a click on the extension's browser action
You may also add commands.update() (Firefox 60+) API to let users change that keyboard shortcut.
Thanks for considering accessibility. Just to clarify, because I don't think you meant this, but you can do keyboard testing without a screen reader. Just don't use your mouse :-) Seriously.
In my current firefox, I have an address bar, the search field, then a bunch of plugins on a toolbar.
On a PC (should be similar for a Mac, but Cmd instead of Ctrl):
I can move my keyboard focus to the address bar with alt+d or ctrl+L (cmd+L)
I can move my keyboard focus to the search field with ctrl+k (cmd+k)
Interestingly enough, I could not get my focus on the toolbar. I could have sworn I could tab from the address field, to the search field, to the toolbar, but it's not working now.
If you can get your focus there, then you should be able to use the left/right arrows to move between tools and then space/enter to select the tool.
If you want to play with a screen reader, NVDA is free.

CSS media query for whether a physical keyboard is attached

Suppose I have a site with keyboard shortcuts, where I want to display said keyboard shortcuts visually as part of whatever element they apply to.
On a touch interface, especially a phone, I don't want to bother because:
nobody would use a soft-keyboard this way even if they could
the visual display of the keyboard shortcut takes up valuable real-estate
it's perhaps confusing, or at least inelegant, to display keyboard shortcuts in a keyboardless context
However, the media query documentation doesn't seem to mention anything about this.
It's 2016, is this still impossible?
Unfortunately there is no query in Media Queries 4 to identify the existence of a keyboard.
There are other new queries though that might be helpful.
In my own application I'm assuming that a keyboard exists when there is a mouse or a touchpad as primary input. You can query for that with
#media (hover: hover) and (pointer: fine) { ... }
This query would go false for devices with a touchscreen, stylus devices and also exotic devices like camera input.
Note that with this query you're querying for primary input devices. You can query all input devices with
any-hover and any-pointer.
Also note that as of date, the adoption for MQ4 is 81% of all browsers, but no Firefox: https://caniuse.com/#feat=css-media-interaction
Media Queries 4 does not provide any media features for determining whether a physical keyboard is attached. There's nothing stopping you from proposing such a feature for MQ4 or MQ5 over at the www-style mailing list, though keep in mind whether such a media feature would be easy for vendors to implement is another story.

CSS Selector :focus not working with Chromecast

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.

How to develop website/application to view in tablet pc?

I am developing website and it has to be viewed in tablet pc. Please suggest me what are things to be considered ? technology wise ?
also i need to know what are the tools i need to have to view in my intranet as well as.
A major issue: in many tablets there is no moving pointer - at least not in a fully usable form. That means that tooltips may not really work, and image maps must be really clear, since there is no highlighting until the user actually "clicks" on the link.
Well, actually that's not fully accurate - if the user drags the pointer, it should work like a regular mouse pointer. The problem is that most users avoid dragging and just tap where they want to click directly.
Best piece of advice I can offer: get an actual tablet PC and try browsing your site. Most major issues will be evident almost immediately. If you are able, get a regular tablet/pad user to beta-test your site without trying it out on a desktop PC - they would be able to see issues that you would miss due to your prior knowledge of the site.
The Tablet PC is a standard Windows machine, therefore it has the same browser support as any other Windows box. So there isn't any special technology required.
There are however some design considerations:
First, make sure your layout has plenty of empty space surrounding iterative elements. Crammed pages are tough to navigate with a stylus, and if it is one of the newer models that also support touch it is even more of an issue.
Second, most Tablet PCs are configured with the default font size set for 125%. You want to make sure that your web pages scale correctly and don't end up requiring horizontal scrolling to see the full width of the page.
A second point regarding scaling, Tablet PC supports both Landscape and Portrait modes. In other words, it can be 1024x768 OR 768x1024. You'll want to make sure that your user experience is acceptable in both modes.
One thing i can think of : there is no 'hover' on most tablets, and if it's there at all, likely nobody will see it.
Not all tablets support flash, but they do all support javascript, and Prototype.JS or jQuery will run on them in most cases

Can I make a website full screen without flash or silverlight?

I'm working on something that needs a webpage to go full screen. The screen must become completely white.
Is there anyway that I can do this without flash or silverlight?
Thanks in advance
edit: Im not trying to force anybody into fullscreen, this will be mainly used by a couple of people. Even so I'll give proper feedback on how to get in and out of fullscreen .
You cant do full screen, because of security reasons the title bar is still there and so on in different browsers.
But a way could be to make the window larger than the screen, lets say 100 pixels wider and 100 pixels higher and position the window at -50, -50. I havent tried that but if there is no restrains against window size being bigger than screen size it could be a solution.
With JavaScript:
window.open ("http://stackoverflow.com", "","fullscreen=yes");
The size of the window varies between browsers, but actually in IE, you will have the desired behavior...
Please dont resize the user's web browser. I use the rest of my screen for other things, and I think many users do too. A respectful website stays where the browser puts it.
"Something like ajax for example?"...
Ajax != Javascript.
Your responsibility as a web site operator is to have some manners and allow the user to control the size.
You could read the screen.width and screen.height and if they are far off the document.body.clientHeight or document.body.clientWidth, alert the user that the page should be viewed in fullscreen mode and how to make it fullscreen (F12 for IE - i think, F11 for FF).
No, you can't control the browser in that way with javascript.
You can instruct your users to use firefox 3, and press F11 to enter full screen mode. the title bar will go away if the mouse isn't near the top of the screen.
Yes, it requires user interaction, but if they want to go into full screen then it's easy for them to do so under their own power, and to leave again when they want to.
-Adam
Well, I see that you are trying to simply have a button that will make the page full-screen; similar to the youtube full screen mode.
As well, I do NOT suggest using the "just hit F11" method, as people on Safari, or Mac in general, will be excluded.
You can use C#, which can be done by downloading Visual Studio or MS Visulal C#, or even CosmosBoot. There is plenty of code for full screen applications in C#. Another good thing about full screen in C# is that it can be easily embedded into a webpage, through some simplye ASP code.
You can use java, which can be painfully slow, and require a lot of coding, but it is attainable. You can use one of several hundred IDEs or JDKs, but I don't really use java, so I can't give you much in the way of advice on programming it, but it is EVEN EASIER to embed than C#, all you need is the tag.

Resources