DiskBoss provides a built-in disk SMART viewer allowing one to view the health status of physical hard disks installed in the computer.In order to open the disk SMART viewer, press the 'SMART' button located on the main toolbar. The disk SMART viewer shows the disk model name,the firmware version, the disk serial number and the list of supported SMART attributes for the currently selected physical disk.
If multiple physical disks are installed in the computer, use the disk selector combo box, located on the bottom side of the SMART viewer,to change the currently displayed disk. If one or more critical SMART attributes are out of valid ranges, the attributes will be markedwith yellow (warning) icons or red (error) icons depending on the status and meaning of each specific SMART attribute.
In the reference design, BOE, which Qualcomm partnered with in April last year, provides a micro-OLED binocular display, that allows frame rates to achieve up to 90 Hz and a no-motion-blur feature to deliver a seamless AR experience, according to Qualcomm. The AR smart viewer hardware, developed by Goertek, enables manufacturers to quickly scale and develop smart AR devices for commercial use.
According to Swart, the future will involve having some processing on the glass itself, but not all of it. This is mainly due to the power constraints of small form factor eyeglasses. The next logical step is going wireless from the phone to the glass, but once you do that, you do require processing in the glass. The smart viewer reference design is therefore part of this journey from simple viewers (such as the Nreal Light) to true smart glasses.
The company too is working on wireless, but in two segments. One is from the glass to a phone or host device, and the other is from the phone/host device to the cloud. Ultimately the end goal is to have all of the heavy rendering carried out on the cloud, with a smart glasses-style device then able to receive the information over wireless (5G or 6G). This is still going to take a long time before the technology is capable of doing this though. The local link between the glass and phone does however mark a very important development towards this goal.
On Tuesday, Qualcomm revealed its own XR1 AR Smart Viewer Reference Design, a pair of smartglasses that are meant to give OEMs (original equipment makers) an easy solution for launching their own smartglasses products.
Qualcomm's XR1 offers a dynamic that allows the user to connect the smartglasses to a PC, an external puck computing unit, or even a smartphone. Manufacturers adopting the XR1 will be able to harness the device's dual monochrome cameras, which enable six- degrees of freedom (6DoF), as well as image stabilization.
This new reference design will likely pave the way for something we've been predicting for some time, which is a wave of birth bath style AR smartglasses from China now that a simple solution for using an Android smartphone as the primary computing unit for a pair of AR smartglasses has been normalized.
The suggested workflow is to take the default CSS file for the appropriate viewer, copy it to a different location, customize it, and specify the location of the customized file in the style= command.
Custom CSS file must contain the same class declarations as the default one. If a class declaration is omitted, the viewer does not function properly because it does not provide built-in default styles for user interface elements.
When you create custom CSS, remember that the viewer assigns .s7smartcropvideoviewer class to its container DOM element. If you use an external CSS file that is passed with the style= command, use .s7smartcropvideoviewer class as parent class in descendant selector for your CSS rules. If you embed styles on the web page, also qualify this selector with an ID of the container DOM element as follows:
To help with creating responsive designed CSS, the viewer supports CSS markers which special CSS classes dynamically assigned to the top-level viewer container element. This assignment is based on the run-time viewer size and the input type used on the current device.
The first group of CSS markers includes .s7size_large, .s7size_medium, and .s7size_small classes. They are applied based on the runtime area of the viewer container. That is, if the viewer area is equal to or bigger than the size of a common desktop monitor .s7size_large is used; if the area is close in size to a common tablet device .s7size_medium is assigned. For areas similar to mobile phone screens, .s7size_small is set. The primary purpose of these CSS markers is to create different user interface layouts for different screens and viewer sizes.
The second group of CSS markers includes .s7mouseinput and .s7touchinput. The marker .s7touchinput is set if the current device has touch input capabilities; otherwise, .s7mouseinput is used. These markers are intended to create user interface input elements with different screen sizes for different input types, because normally touch input requires larger elements. In case the device has both mouse input and touch capabilities, .s7touchinput is set and the viewer renders a touch-friendly user interface.
The following sample CSS sets the play/pause button size to 28 x 28 pixels on systems with mouse input, and 56 x 56 pixels on touch devices. In addition, it hides the button completely if the viewer size becomes small:
Using CSS markers is the most flexible way of building responsive designed CSS. This flexibility lets you target not only device screen size but actual viewer size, which may be useful for responsive design page layouts.
All paths to external assets within CSS are resolved against the CSS location not the location of the viewer HTML page. Remember this rule when you copy the default CSS to a different location. Copy the default assets or update paths within the custom CSS.
When customizing the viewer user interface with CSS, the use of the !IMPORTANT rule is not supported to style viewer elements. In particular, !IMPORTANT rule should not be used to override any default or run-time styling provided by the viewer or Viewer SDK. The reason is that it may affect the behavior of proper components. Instead, you should use CSS selectors with the proper specificity to set CSS properties that are documented in this reference guide.
When the Account Representative starts a product demo, he/she updates the status of the demo to "In Progress". Using this smart service, you can have an event feed entry generated automatically when the Account Representative updates this status so other staff members can see additional information on the potential client including the main focus of the demonstration and who is conducting the demonstration.
Sometimes, you may need two viewers so that you can play back and skim event clips separately from timeline clips. The event viewer is a separate video display that appears next to the main viewer. With the event viewer and the viewer open, you can display two clips at the same time: one from the browser and one from the timeline.
You use the event viewer to play clips in the browser only. As you do with the main viewer, you can show video scopes, color channels, title and action safe zones, and multicam angles (with the event viewer set to show angles). Playback and adjustment controls are identical in the viewer and the event viewer. Other viewer-related operations (including onscreen controls and built-in effects) are done with the main viewer.
ZTE will also be showcasing a variety of other devices, including the Grand S II, nubia 5S and nubia 5S mini smartphones, the Iconic Phablet, and a wearable device called the BlueWatch. The full press release can be found below.
08ab062aa8