Your version of Internet Explorer is either running in "Compatibility View" or is too outdated to display this site. If you believe your version of Internet Explorer is up to date, please remove this site from Compatibility View by opening Tools > Compatibility View settings (IE11) or clicking the broken page icon in your address bar (IE9, IE10)
Missouri S&T - Missouri University of Science and Technology
- Future Students
- Current Students
- Faculty and Staff
Environmental Health and Safety
- 200 Technology Development Center, 900 Innovation Drive, Rolla, MO 65409
- (573) 341-4305
- [email protected]
- General Safety
- Ergonomic Workstation Guide
Ergonomic Guide for Visual Display Terminal (VDT) Computer Workstations
Computers have revolutionized the way we work. People whose occupations involve spending prolonged periods of time at a computer workstation are subjected to stressors that may lead to painful, debilitating conditions.
Adjustable chairs and desks, well-designed keyboards and proper lighting all contribute to the reduction of stressors that can be placed on the Visual Display Terminal (VDT) worker. The resulting stress may cause higher levels of fatigue and tension during the day. You can be more re comfortable and productive when ergonomic thinking is applied to the computer workstation.
Prolonged exposure to a non ergonomic working environment may lead to the development of Cumulative Trauma Disorders, or CTD's. CTD's are problems that arise slowly and unnoticeably over time which can lead to injury or disability. Even small adjustments to the workstation environment can lead to greater comfort and reduce the chance of future injury occurring. Read on to learn how ergonomics can make the computer workstation better--and healthier--for you.
Cumulative Trauma Disorders, or CTD's are a class of injuries that arise from putting excessive pressure on the body to perform over a period of time. Four major factors contribute to their development:
- Awkward or non-optimal body positions
- Frequency of Repetition
Even small forces with high frequencies of repetition may cause or contribute to CTD's.
The most common CTD's among VDT users are:
Back and shoulder problems can be caused by stresses due to sitting without good back support or improper heights of the workstation relative to the body, often created by poor chair height adjustment. Lack of flexibility in workstation design can also contribute to these problems.
Tendinitis is an inflammation of a tendon, usually near a joint or bony surface. Often, tendinitis caused by office work occurs in the lower arm/hand or shoulder regions.
Carpal Tunnel Syndrome is a specific injury that often begins as tendinitis in the wrist or hand area and becomes progressively worse, leading to other problems. The thumb and first two or three fingers are affected due to median nerve involvement. Repetitive motions such as typing extensively with the wrists in a bent position can contribute to the onset of carpal tunnel syndrome.
The Cumulative Trauma Disorder usually begins when a VDT user does not address working situations that are merely bothersome. Over time, the slight irritation being experienced may develop into a serious injury.
Applying ergonomic thinking to workstations can result in a reduced chance of CTD's occurring.
THE SEATED POSITION
The chair is a key component in the ergonomics of a computer workstation. A good chair is one that allows you to maintain a variety of comfortable task positions while working throughout the day.
While there is no "perfect" working posture for everyone, the following guidelines are useful for improving the body geometry of the workstation:
- The seat height should be adjusted so that the thighs are nearly horizontal and the feet are resting flat and comfortably on the floor.
- Use a footrest if your feet are not resting comfortably on the floor.
- When the chair orientation has the user placing the feet flat on the floor or on a support, the resulting angle between the upper and lower legs should be from 60 to 100 degrees.
- The angle between the seat pan and seat back should permit the person to assume a working posture in which the thigh-torso angle is not less than 90 degrees, with 100 degrees as preferable.
- The chair should have a backrest with support for the curvature in the lower back. The backrest should be adjusted to fit your individual spinal curvature for maximum comfort.
Feeling tension in your legs, back or shoulders could be a sign of poor chair adjustment, such that it is not providing the body adequate support.
Sometimes sitting in a stationary position for a long period of time can lead to muscle fatigue. Moving your body around during the day can help reduce muscle strains and lower wear and tear on your disks and spine.
A key point to remember is that you should be able to rest your feet flat on the floor without the chair putting pressure on the backs of your legs, which may in turn reduce whole-body blood circulation.
PROPER POSTURE DURING VDT USE
Proper posture while using a VDT can help prevent tension or stiffness in the neck, back and shoulders.
Use these posture checkpoints to reduce stress on the muscle and skeletal system:
- Keep your elbows close to your sides. This will reduce upper back and shoulder muscle tension.
- Try to maintain a 90 degree angle between the upper and lower arm. This is considered "neutral," although any position between 70 and 135 degrees is acceptable.
- Hold the wrist and forearm in a straight line to reduce tendon and nerve stress. The forearm should be roughly parallel to the floor.
- Ideally, your wrist should be supported near the keyboard by a wrist support to help provide a neutral (straight) arm/wrist position.
- Adjust the keyboard to a slope between 0 and 25 degrees.
- Keep your head up, with the ideal VDT about 48 to 25 inches from your eyes. The minimum acceptable eye-to=screen distance is 12 inches.
- Maintain a line of sight from your eyes to the screen's primary viewing area that is between 0 and 60 degrees below the horizon. The optimal viewing angle is 20 degrees below the horizon.
Following these guidelines helps your body maintain a healthy, natural geometry at the VDT. For best results, stay within stated ranges when making adjustments for individual preference.
VISION AND LIGHTING
Screen clarity to the eye and office lighting both affect your well being when using a VDT. Some technical parameters of the VDT screen, as well as the eye itself, are influencing factors.
Here are guidelines for the best interaction between the VDT screen and your eyes.
- Remember that glare from outside light sources creates eye strain.
- Try to position the VDT at a 90 degree angle to strong light sources such as windows or bright lights.
- Adjust screen angle if needed to reduce glare.
- Consider using screen filters to reduce glare if other methods fail.
- Make sure that the screen has adequate character resolution and luminance. Adjust the screen intensity if necessary.
- Avoid displays that have a perceptible "flitter."
- Avoid intense light sources in your peripheral field of vision if possible.
- Place your document holder near the screen and in the same plane as the screen to avoid eye strain and fatigue.
- Take breaks as your work schedule permits to get your eyes focused off of the screen and into the distance to relax the eye muscles.
- See your eye healthcare professional if you experience any visual discomfort from your VDT work.
Use of computer workstations is becoming the standard in a growing number of occupations. Ergonomics can assure that individuals function most effectively and protect their health as modern technology is applied in more areas of our society.
These general guidelines will help you stay more alert and reduce strain and fatigue while using a VDT:
- Change positions, stretch, or walk around during the day if you begin to feel tired.
- Use a "light touch" on the keyboard to reduce hand stress and lower your risk of developing CTD's
- Rest your eyes throughout the day.
- Keep the VDT screen and your eyeglasses clean.
Following the guidelines contained in this web page will help you to be more productive and enhance the health and well-being of your body. At the end of the day, you will also feel better and enjoy your leisure hours free of pain and stiffness.
If problems should arise, consult a health care professional as soon as possible to avoid potential injury or the development of a disabling condition.
Environmental Health and Safety Missouri University of Science and Technology
Missouri University of Science and Technology
- Missouri S&T, Rolla, MO 65409
- [email protected]
- Work at S&T
- Police and Parking
- S&T Alerts
- Give to S&T
- Student Accessibility and Testing
- Social Media Directory
- All S&T Accounts
Missouri S&T is an equal opportunity/access/affirmative action/pro-disabled and veteran employer and does not discriminate on the basis of sex in our education programs or activities, pursuant to Title IX and 34 CFR Part 106. For more information, see S&T's Nondiscrimination Policy or Equity and Title IX . © 2022 Curators of the University of Missouri.
- Consumer Information
Version 1.76 is now available! Read about the new features and fixes from February.
Visual Studio Code includes a full featured integrated terminal that conveniently starts at the root of your workspace. It provides integration with the editor to support features like links and error detection .
To open the terminal:
- Use the ⌃` (Windows, Linux Ctrl+` ) keyboard shortcut to toggle the terminal panel.
- Use the ⌃⇧` (Windows, Linux Ctrl+Shift+` ) keyboard shortcut to create a new terminal.
- Use the View > Terminal or Terminal > New Terminal menu commands.
- From the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ), use the View: Toggle Terminal command.
Note: Open an external terminal with the ⇧⌘C (Windows, Linux Ctrl+Shift+C ) keyboard shortcut if you prefer to work outside VS Code.
The integrated terminal can use various shells installed on your machine, with the default being pulled from your system defaults. Shells are detected and presented in the terminal profiles dropdown.
You can learn more about configuring terminal shells in the terminal profiles article.
The terminal tabs UI is on the right side of the terminal view. Each terminal has an entry with its name, icon, color, and group decoration (if any).
Terminal instances can be added by selecting the + icon on the top-right of the TERMINAL panel, selecting a profile from the terminal dropdown, or by triggering the ⌃⇧` (Windows, Linux Ctrl+Shift+` ) command. This action creates another entry in the tab list associated with that terminal.
Remove terminal instances by hovering a tab and selecting the Trash Can button, selecting a tab item and pressing Delete , using Terminal: Kill the Active Terminal Instance command, or via the right-click context menu.
Navigate between terminal groups using focus next ⇧⌘] (Windows, Linux Ctrl+PageDown ) and focus previous ⇧⌘[ (Windows, Linux Ctrl+PageUp ) .
Icons may appear to the right of the terminal title on the tab label when a terminal's status changes. Some examples are a bell (macOS) and for tasks, displaying a check mark when there are no errors and an X otherwise. Hover the icon to read status information, which may contain actions.
Groups (split panes)
Multiple terminals can be placed side-by-side are called a group and are created by splitting a terminal:
- On hover, selecting the inline split button.
- Right-clicking the context menu and selecting the Split menu option.
- Alt and click on a tab, the + button, or the single tab on the terminal panel.
- Triggering the ⌘\ (Windows, Linux Ctrl+Shift+5 ) command.
Tip: The working directory for the new terminal depends on the terminal.integrated.splitCwd setting .
Navigate between terminals in a group by focusing the previous pane, ⌥⌘← (Windows, Linux Alt+Left ) , or the next pane, ⌥⌘→ (Windows, Linux Alt+Right ) .
Dragging and dropping tabs in the list will rearrange them. Dragging a tab into the main terminal area allows moving a terminal from one group to another.
Moving a terminal into its own group can be done with the Terminal: Unsplit Terminal command through the Command Palette or in the right-click context menu.
Terminals in editor area
Terminal in the editor area, also known as terminal editors, can be created through the Terminal: Create New Terminal in Editor Area and Terminal: Create New Terminal in Editor Area to the Side commands or by dragging a terminal from the terminal view into the editor area.
Terminal editors are ideal if you want a complex workbench layout such as terminals on either side of an editor or terminals arranged in two dimensions. Below PowerShell and WSL terminals are stacked in an editor group to the right of a group of file editors.
The terminal.integrated.defaultLocation setting can change the default terminal location to be in either the view or editor areas.
Navigating the buffer
The content in the terminal is called the buffer, with the section right above the bottom viewport being called "scrollback". The amount of scrollback kept is determined by the terminal.integrated.scrollback setting and defaults to 1000 lines.
There are various commands available to navigate around the terminal buffer:
- Scroll up a line - ⌥⌘PageUp (Windows Ctrl+Alt+PageUp , Linux Ctrl+Shift+Up )
- Scroll down a line - ⌥⌘PageDown (Windows Ctrl+Alt+PageDown , Linux Ctrl+Shift+Down )
- Scroll up a page - PageUp (Windows, Linux Shift+PageUp )
- Scroll down a page - PageDown (Windows, Linux Shift+PageDown )
- Scroll to the top - ⌘Home (Windows Ctrl+Home , Linux Shift+Home )
- Scroll to the bottom - ⌘End (Windows Ctrl+End , Linux Shift+End )
Command navigation is also available (see shell integration ):
- Scroll to the previous command - ⌘↑ (Windows, Linux Ctrl+Up )
- Scroll to the next command - ⌘↓ (Windows, Linux Ctrl+Down )
Scrolling will happen instantaneously, but can be configured to animate over a short duration with the terminal.integrated.smoothScrolling setting.
The terminal features sophisticated link detection with editor integration and even extension contributed link handlers. Links are activated by mousing over the link so an underline appears, then hold Ctrl / Cmd and click.
There are several built-in link handlers that are used in the following priority order:
URIs/URLs: These are links that look like URIs, such as https://code.visualstudio.com , vscode://file/path/to/file or file://path/to/file . These will open using the standard handler for the protocol. For example, https links will open the system browser at that location.
File links: These are links to files that have been verified to exist on the system. These will open the file in a new editor tab and support many common line/column formats such as file:1:2 , file:line 1, column 2 .
Folder links: These are similar to file links but will open a new VS Code window at the folder.
Word links: This is the fallback link type and uses the terminal.integrated.wordSeparators setting to define word boundaries and make nearly all text into words. Activating a word link will search the workspace for the word, if there is a single result it will open, otherwise it will present the search results. Word links are considered "low confidence" and will not show an underline or tooltip unless Ctrl / Cmd is held. They also have limited support for line and column suffixes.
The Open Detected Link command ( ⇧⌘O (Windows, Linux Ctrl+Shift+O ) ) can be used to access links via the keyboard:
Tip: If link verification causes performance issues, like in high latency remote environments, it can be disabled via the terminal.integrated.enableFileLinks setting .
Extensions handling links
Extensions can contribute link providers which allow the extension to define what happens when clicked. An example of this is the GitLens extension detecting Git branch links.
Links are keyboard accessible through several commands that open links based on the type of link.
- Terminal: Open Last Local File Link - Opens the most recent local file link. No default keybinding.
- Terminal: Open Last URL link - Opens the most recent URI/URL link. No default keybinding.
- Terminal: Open Detected Link... - Opens a searchable Quick Pick with all detected links, including word links. The default keybinding is Ctrl/Cmd+Shift+O , which is the same as the Go to Symbol in Editor keyboard shortcut.
Copy & paste
The keybindings for copy and paste follow platform standards:
- Linux: Ctrl+Shift+C and Ctrl+Shift+V ; selection paste is available with Shift+Insert
- macOS: Cmd+C and Cmd+V
- Windows: Ctrl+C and Ctrl+V
Copying is done automatically on selection when terminal.integrated.copyOnSelection is enabled.
By default there is a warning when pasting multiple lines, which can be disabled with the terminal.integrated.enableMultiLinePasteWarning setting. This is only done when the shell does not support "bracketed paste mode". When that mode is enabled, the shell is indicating that it can handle multiple line pasting.
Using the mouse
The right-click behavior differs based on the platform:
- Linux: Show the context menu.
- macOS: Select the word under the cursor and show the context menu.
- Windows: Copy and drop selection if there is a selection, otherwise paste.
This can be configured using the terminal.integrated.rightClickBehavior setting. The options are:
- default - Show the context menu.
- copyPaste - Copy when there is a selection, otherwise paste.
- paste - Paste on right-click.
- selectWord - Select the word under the cursor and show the context menu.
- nothing - Do nothing and pass event to terminal.
Reposition the cursor with Alt
Alt and left-click will reposition the cursor to underneath the mouse. This works by simulating arrow keystrokes, which may not work reliably for some shells or programs. This feature can be disabled with the terminal.integrated.altClickMovesCursor setting.
Mouse events mode
When applications running in the terminal turn on mouse events mode, such as Vim mouse mode, mouse interaction is sent to the application instead of the terminal. This means that clicking and dragging will no longer create a selection. Terminal selection can be forced by holding the Alt key on Windows and Linux, this can also be done with the Option key on macOS but requires enabling the terminal.integrated.macOptionClickForcesSelection setting first.
The integrated terminal has find functionality that can be triggered with ⌘F (Windows, Linux Ctrl+F ) .
Tip: Ctrl+F can be sent to the shell by removing the workbench.action.terminal.focusFind command from commands to skip shell .
Run selected text
To use the runSelectedText command, select text in an editor and run the command Terminal: Run Selected Text in Active Terminal via the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ), the terminal will attempt to run the selected text. If no text is selected in the active editor, the entire line that the cursor is on will run in the terminal.
Tip: Also run the active file using the command workbench.action.terminal.runActiveFile .
Maximizing the terminal
The terminal view can be maximized by clicking the maximize panel size button with the upwards chevron icon. This will temporarily hide the editors and maximize the panel. This is useful to temporarily focus on a large amount of output. Some developers use VS Code as a standalone terminal by opening a new window, maximizing the panel, and hiding the side bar.
There is a Terminal: Select All command, which is bound to Cmd+A on macOS, but does not have a default keybinding on Windows and Linux as it may conflict with shell hotkeys. To use Ctrl+A to select all, add this custom keybinding:
Drag and drop file paths
Dragging a file into the terminal will input the path into the terminal, with escaping to match the active shell.
Automating terminals with tasks
The Tasks feature can be used to automate the launching of terminals, for example, the following .vscode/tasks.json file will launch a Command Prompt and PowerShell terminal in a single terminal group when the window starts:
This file could be committed to the repository to share with other developers or created as a user task via the workbench.action.tasks.openUserTasks command.
By default, the terminal will open at the folder that is opened in the Explorer. The terminal.integrated.cwd setting allows specifying a custom path to open instead:
Split terminals on Windows will start in the directory that the parent terminal started with. On macOS and Linux, split terminals will inherit the current working directory of the parent terminal. This behavior can be changed using the terminal.integrated.splitCwd setting:
There are also extensions available that give more options such as Terminal Here .
Fixed dimension terminals
The Terminal: Set Fixed Dimensions command allows changing the number of columns and rows that the terminal and it's backing psuedoterminal uses. This will add scroll bars when necessary, which may lead to an unpleasant UX and is generally not recommended, but it is a common ask on Windows in particular for reading logs or long lines when paging tools aren't available.
You can also right-click on a terminal tab and select Toggle Size to Content Width ( ⌥Z (Windows, Linux Alt+Z ) ) to resize the number of terminal columns to the largest wrapped line in the terminal.
The basics of the terminal have been covered in this document. Read on to find out more about:
- Tasks - Tasks let you integrate with external tools and leverage the terminal heavily.
- Mastering VS Code's Terminal - An external blog with plenty of power user tips for the terminal.
- Explore terminal commands by browsing the keyboard shortcuts within VS Code ( Preferences: Open Keyboard Shortcuts then search on 'terminal').
I'm having problems launching the terminal.
There's a dedicated troubleshooting guide for these sorts of problems.
Why is nvm complaining about a prefix option when the integrated terminal is launched?
nvm (Node Version Manager) users often see this error for the first time inside VS Code's integrated terminal:
This is mostly a macOS problem and does not happen in external terminals. The typical reasons for this are the following:
- npm was globally installed using another instance of node that is somewhere in your path (such as /usr/local/bin/npm ).
- To get the development tools on the $PATH , VS Code will launch a bash login shell on startup. This means that your ~/.bash_profile has already run and when an integrated terminal launches, it will run another login shell, reordering the $PATH potentially in unexpected ways.
To resolve this issue, you need to track down where the old npm is installed and remove both it and its out-of-date node_modules. Find the nvm initialization script and run which npm before it runs, which should print the path when you launch a new terminal.
Once you have the path to npm, find the old node_modules by resolving the symlink by running a command something like this:
This will give you the resolved path at the end:
From there, removing the files and relaunching VS Code should fix the issue:
Why does macOS make a ding sound when I resize terminal split panes?
The keybindings ⌃⌘← and ⌃⌘→ are the defaults for resizing individual split panes in the terminal. While they work, they also cause a system "invalid key" sound to play due to an issue in Chromium. The recommended workaround is to tell macOS to no-op for these keybindings by running this in your terminal:
I'm having problems with the terminal rendering. What can I do?
By default, the integrated terminal will render using GPU acceleration on most machines. Typically when there are rendering problems it's an issue of something in your hardware/OS/drivers not playing nicely with the GPU renderer. The first thing to try is to disable GPU acceleration, trading off rendering speed for DOM-based rendering, which is more reliable:
See the GPU acceleration section for more information.
I see 1~ or [201~ when I paste something
This normally means that the program/shell running inside the terminal requested to turn on "bracketed paste mode" but something doesn't support it properly. To work around this, you could run printf "\e[?2004l" to disable it for that session or add the following to your ~/.inputrc file:
Ctrl+A, Ctrl+R output ^A, ^R on zsh
This can happen if zsh is in Vim mode instead of Emacs mode, due to setting $EDITOR or $VISUAL to vi / vim in your init scripts.
To work around this, you have two options:
- Ensure that you don't set $EDITOR to vi(m) . However, this isn't an option if you want your Git editor to work.
- Add bindkey -e to your init script to set Emacs explicitly.
How can I configure Cmd+. to map to Ctrl+C like macOS' built-in terminal?
The macOS default terminal uses Cmd+. to perform the same as Ctrl+C . To get this behavior in VS Code, add this custom keybinding :
Why are the colors in the terminal not correct?
One of our accessibility features we enable by default is to ensure a minimum contrast ratio of at least 4.5 is met for the foreground text. This feature ensures that text is readable regardless of the shell and theme used which is not possible otherwise. To disable this feature, you can set:
See the minimum contrast ratio section for more information.
An official website of the United States government
The .gov means it’s official. Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.
The site is secure. The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.
- Account settings
- My Bibliography
- Citation manager
Save citation to file
Email citation, add to collections.
- Create a new collection
- Add to an existing collection
Add to My Bibliography
Your saved search, create a file for external citation management software, your rss feed.
- Search in PubMed
- Search in NLM Catalog
- Add to Search
Review on the possible pathophysiological mechanisms underlying visual display terminal-associated dry eye disease
- 1 Institute of Clinical Medicine, Faculty of Medicine, University of Oslo, Oslo, Norway.
- 2 Department of Medical Biochemistry, Oslo University Hospital, Oslo, Norway.
- 3 Department of Plastic and Reconstructive Surgery, Oslo University Hospital, Oslo, Norway.
- 4 Department of Ophthalmology, University of Groningen, University Medical Center Groningen, Groningen, The Netherlands.
- 5 Schepens Eye Research Institute of Massachusetts Eye and Ear, Harvard Medical School, Boston, Massachusetts, USA.
- 6 Department of Twin Research & Genetic Epidemiology, King's College London, St Thomas' Hospital, London, UK.
- 7 Department of Epidemiology, University of Groningen, University Medical Center Groningen, Groningen, The Netherlands.
- 8 Department of Ophthalmology, Oslo University Hospital, Oslo, Norway.
- 9 Department of Ophthalmology, Sørlandet Hospital Arendal, Arendal, Norway.
- 10 Department of Quality and Health Technology, The Faculty of Health Sciences, University of Stavanger, Stavanger, Norway.
- 11 Department of Ophthalmology, Stavanger University Hospital, Stavanger, Norway.
- 12 Department of Computer Science, Oslo Metropolitan University, Oslo, Norway.
- 13 Department of Clinical Medicine, Faculty of Medicine, University of Bergen, Bergen, Norway.
- PMID: 35441459
- PMCID: PMC9790214
- DOI: 10.1111/aos.15150
Background: Visual display terminal (VDT) use is a key risk factor for dry eye disease (DED). Visual display terminal (VDT) use reduces the blink rate and increases the number of incomplete blinks. However, the exact mechanisms causing DED development from VDT use have yet to be clearly described.
Purpose: The purpose of the study was to conduct a review on pathophysiological mechanisms promoting VDT-associated DED.
Methods: A PubMed search of the literature investigating the relationship between dry eye and VDT was performed, and relevance to pathophysiology of DED was evaluated.
Findings: Fifty-five articles met the inclusion criteria. Several pathophysiological mechanisms were examined, and multiple hypotheses were extracted from the articles. Visual display terminal (VDT) use causes DED mainly through impaired blinking patterns. Changes in parasympathetic signalling and increased exposure to blue light, which could disrupt ocular homeostasis, were proposed in some studies but lack sufficient scientific support. Together, these changes may lead to a reduced function of the tear film, lacrimal gland, goblet cells and meibomian glands, all contributing to DED development.
Conclusion: Visual display terminal (VDT) use appears to induce DED through both direct and indirect routes. Decreased blink rates and increased incomplete blinks increase the exposed ocular evaporative area and inhibit lipid distribution from meibomian glands. Although not adequately investigated, changes in parasympathetic signalling may impair lacrimal gland and goblet cell function, promoting tear film instability. More studies are needed to better target and improve the treatment and prevention of VDT-associated DED.
Keywords: DED; VDT; VDT-associated dry eye; dry eye disease; pathophysiology; tear film.
© 2022 The Authors. Acta Ophthalmologica published by John Wiley & Sons Ltd on behalf of Acta Ophthalmologica Scandinavica Foundation.
Tear film and important associated…
Tear film and important associated structures. Meibomian glands, the lacrimal gland and goblet…
Interblink interval (IBI) and tear…
Interblink interval (IBI) and tear film break‐up time (TBUT) in two different settings.…
Flowchart of the stepwise search…
Flowchart of the stepwise search strategy and methodology.
Possible mechanisms involved in visual…
Possible mechanisms involved in visual display terminal (VDT)‐associated dry eye development. Visual display…
Ocular protection index (OPI) is…
Ocular protection index (OPI) is the ratio between the tear film break‐up time…
Possible effects of blue light…
Possible effects of blue light on the ocular surface. Blue light emitted by…
- Video display terminal use and dry eye: preventive measures and future perspectives. Kamøy B, Magno M, Nøland ST, Moe MC, Petrovski G, Vehof J, Utheim TP. Kamøy B, et al. Acta Ophthalmol. 2022 Nov;100(7):723-739. doi: 10.1111/aos.15105. Epub 2022 Feb 4. Acta Ophthalmol. 2022. PMID: 35122403 Free PMC article. Review.
- The association between visual display terminal use and dry eye: a review. Fjaervoll H, Fjaervoll K, Magno M, Moschowits E, Vehof J, Dartt DA, Utheim TP. Fjaervoll H, et al. Acta Ophthalmol. 2022 Jun;100(4):357-375. doi: 10.1111/aos.15049. Epub 2021 Oct 25. Acta Ophthalmol. 2022. PMID: 34697901 Review.
- Evaluation of incomplete blinking as a measurement of dry eye disease. Jie Y, Sella R, Feng J, Gomez ML, Afshari NA. Jie Y, et al. Ocul Surf. 2019 Jul;17(3):440-446. doi: 10.1016/j.jtos.2019.05.007. Epub 2019 May 29. Ocul Surf. 2019. PMID: 31152804
- Objective optical assessment of tear-film quality dynamics in patients with meibomian gland dysfunction and aqueous-deficient dry eye optical quality changes in different dry eye subtypes. Ye F, Jiang F, Lu Y, Xue CY, Zhu XM, Wu Y, Huang ZP. Ye F, et al. Indian J Ophthalmol. 2019 May;67(5):599-603. doi: 10.4103/ijo.IJO_1278_18. Indian J Ophthalmol. 2019. PMID: 31007216 Free PMC article.
- Effect of incomplete blinking on tear film stability. Hirota M, Uozato H, Kawamorita T, Shibata Y, Yamamoto S. Hirota M, et al. Optom Vis Sci. 2013 Jul;90(7):650-7. doi: 10.1097/OPX.0b013e31829962ec. Optom Vis Sci. 2013. PMID: 23770659
- Prevalence of Dry Eye Symptoms and Associated Risk Factors among University Students in Poland. Wróbel-Dudzińska D, Osial N, Stępień PW, Gorecka A, Żarnowski T. Wróbel-Dudzińska D, et al. Int J Environ Res Public Health. 2023 Jan 11;20(2):1313. doi: 10.3390/ijerph20021313. Int J Environ Res Public Health. 2023. PMID: 36674068 Free PMC article.
- Can Nutrition Play a Role in Ameliorating Digital Eye Strain? Lem DW, Gierhart DL, Davey PG. Lem DW, et al. Nutrients. 2022 Sep 27;14(19):4005. doi: 10.3390/nu14194005. Nutrients. 2022. PMID: 36235656 Free PMC article. Review.
- Aggarwal S & Galor A (2018): What's new in dry eye disease diagnosis? Current advances and challenges. F1000Res 7: F1000 Faculty Rev‐1952. - PMC - PubMed
- Akkaya S, Atakan T, Acikalin B, Aksoy S & Ozkurt Y (2018): Effects of long‐term computer use on eye dryness. North Clin Istanb 5: 319–322. - PMC - PubMed
- Altalhi A, Khayyat W, Khojah O, Alsalmi M & Almarzouki H (2020): Computer vision syndrome among health sciences students in saudi arabia: prevalence and risk factors. Cureus 12: e7060. - PMC - PubMed
- Antona B, Barrio AR, Gascó A, Pinar A, González‐Pérez M & Puell MC (2018): Symptoms associated with reading from a smartphone in conditions of light and dark. Appl Ergon 68: 12–17. - PubMed
- Argilés M, Cardona G, Pérez‐Cabré E & Rodríguez M (2015): Blink rate and incomplete blinks in six different controlled hard‐copy and electronic reading conditions. Invest Ophthalmol Vis Sci 56: 6679–6685. - PubMed
- Search in MeSH
- R01 EY019470/NH/NIH HHS/United States
- NFR 271555/Norges Forskningsråd
- R01 EY029789/NH/NIH HHS/United States
- R01 EY029789/EY/NEI NIH HHS/United States
- R01 EY021292/NH/NIH HHS/United States
LinkOut - more resources
Full text sources.
- Europe PubMed Central
- Ovid Technologies, Inc.
- PubMed Central
- NCI CPTAC Assay Portal
- Citation Manager
NCBI Literature Resources
MeSH PMC Bookshelf Disclaimer
The PubMed wordmark and PubMed logo are registered trademarks of the U.S. Department of Health and Human Services (HHS). Unauthorized use of these marks is strictly prohibited.
Computer and visual display terminals syndrome is a constellation of symptoms ocular as well as extraocular associated with prolonged use of visual display terminals. This syndrome is gaining importance in this modern era because of the widespread use of …
Visual display terminal syndrome is a health problem that occurs when an individual looks at a visual display terminal for a long time. This study aimed to evaluate the quality of YouTube videos on visual display terminal syndrome. YouTube was searched using the keywords "visual display terminal syn …
Ergonomic Guide for Visual Display Terminal (VDT) Computer Workstations Computers have revolutionized the way we work. People whose occupations involve spending prolonged periods of time at a computer workstation are subjected to stressors that may lead to painful, debilitating conditions.
In this paper the VDT issue is considered with reference to: the known physiology of the visual and postural mechanisms; the psychological factors such as fatigue, boredom, stress and performance of operators; and the clinical aspects of ocular comfort.
Prolonged use of visual display terminals (VDTs) has been suggested as an important risk factor for DED. Purpose: This review aims to study the association between DED and VDT use with an emphasis on the prevalence of DED among VDT users and harmful daily duration of VDT use.
Visual display terminals (VDT) are standard equipment for many office workers. Their use, however, may increase the risk of developing adverse conditions related to vision, the musculoskeletal system, and mental health.
To open the terminal: Use the Ctrl+` keyboard shortcut to toggle the terminal panel. Use the Ctrl+Shift+` keyboard shortcut to create a new terminal. Use the View > Terminal or Terminal > New Terminal menu commands. From the Command Palette ( Ctrl+Shift+P ), use the View: Toggle Terminal command.
visual display unit in British English noun computing a device with a screen that displays characters or graphics representing data in a computer memory. It usually has a keyboard or light pen for the input of information or inquiries Abbreviation: VDU Collins English Dictionary. Copyright © HarperCollins Publishers
According to some reports, mainly from Norway and Sweden, visual display terminal work is suspected of causing skin rashes. In three different studies, we have tried to elucidate the question, and the results indicate that there might be a relation between VDT work and aggravation of some common skin diseases such as rosacea, seborrheic and atopic …
Background: Visual display terminal (VDT) use is a key risk factor for dry eye disease (DED). Visual display terminal (VDT) use reduces the blink rate and increases the number of incomplete blinks. However, the exact mechanisms causing DED development from VDT use have yet to be clearly described.