![Stats Stats](https://www.seense.com/menubarstats/images/mbs3_5.png)
(Redirected from Menubar)
Type: String CSS Inheritance: Yes Language Version: ActionScript 3.0 Product Version: Flex 4 Runtime Versions: Flash10, AIR 1.5 The directionality of the text displayed by the component. The allowed values are 'ltr' for left-to-right text, as in Latin-style scripts, and 'rtl' for right-to-left text, as in Arabic and Hebrew. FTE and TLF use this value in their bidirectional text layout. 1.4.0: Added function to display the average/Max/Minimum CPU Usage of each running process for last 1 minute. Added function to display the average/Max/Minimum network input/output data amount for last 1 minute. Added function to display the icon of each process. Added function to show MiniUsage icon of menu bar. 11.05.14: 1.3.0. Step 3: Download and install onto the computer you have issues with. Step 4:Open the program. Step 5: Select your start menu! Step 6: Customize it! There are many different options. (I do not like changing the start button but you can even make your own start button) Step 7: Open the start menu (It will take a min to load) Step 8: Enjoy!
A menu bar is a graphical control element which contains drop-down menus.
The menu bar's purpose is to supply a common housing for window- or application-specific menus which provide access to such functions as opening files, interacting with an application, or displaying help documentation or manuals. Menu bars are typically present in graphical user interfaces that display documents and representations of files in windows and windowing systems but menus can be used as well in command line interface programs like text editors or file managers where drop-down menu is activated with a shortcut or combination key.
Implementations[edit]
Through the evolution of user interfaces, the menu bar has been implemented in different ways by different user interfaces and application programs.
Macintosh[edit]
In the Macintosh operating systems, the menu bar is a horizontal 'bar' anchored to the top of the screen. In macOS, the left side contains the Apple menu, the Application menu (its name will match the name of the current application) and the currently focused application's menus (e.g. File, Edit, View, Window, Help). On the right side, it contains menu extras (for example the system clock, volume control, and the Fast user switching menu (if enabled) and the Spotlight icon. All of these menu extras can be moved horizontally by command-clicking and dragging left or right. If an icon is dragged and dropped vertically it will disappear with a puff of smoke, much like the icons in the dock. In the Classic Mac OS (versions 7 through 9), the right side contains the application menu, allowing the user to switch between open applications. In Mac OS 8.5 and later, the menu can be dragged downwards, which would cause it to be represented on screen as a floating palette.
There is only one menu bar, so the application menus displayed are those of the application that is currently focused. Therefore, for example, if the System Preferences application is focused, its menus are in the menu bar, and if the user clicks on the Desktop which is a part of the Finder application, the menu bar will then display the Finder menus.
Apple experiments in GUI design for the Lisa project initially used multiple menu bars anchored to the bottom of windows, but this was quickly dropped in favor of the current arrangement,[1] as it proved slower to use (in accordance with Fitts's law). The idea of separate menus in each window or document was later implemented in Microsoft Windows and is the default representation in most Linux desktop environments.
Even before the advent of the Macintosh, the universal graphical menu bar appeared in the Apple Lisa in 1983. It has been a feature of all versions of the Classic Mac OS since the first Macintosh was released in 1984, and is still used today in macOS.
Microsoft Windows[edit]
The menu bar in Microsoft Windows is usually anchored to the top of a window under the title bar; therefore, there can be many menu bars on screen at one time. Menus in the menu bar can be accessed through shortcuts involving the Alt key and the mnemonic letter that appears underlined in the menu title. Additionally, pressing Alt or F10 brings the focus on the first menu of the menu bar.
Linux and UNIX[edit]
Screenshot of KDE 3.5 showing multiple menu bars
Screenshot of KDE 3.5 configured with a single menu bar
KDE and GNOME[2] allow users to turn Macintosh-style and Windows-style menu bars on and off. KDE can have both types in use at the same time.
The standard GNOME desktop uses a menu bar at the top of the screen, but this menu bar only contains Applications and System menus and status information (such as the time of day); individual programs have their own menu bars as well. The Unity desktop shell shipped with Ubuntu Linux since version 11.04 uses a Macintosh-style menu bar; however, it is hidden unless the mouse pointer hovers over it, similar to the Amiga example below.
Other window managers and desktop environments use a similar scheme, where programs have their own menus, but clicking one or more of the mouse buttons on the root window brings up a menu containing, for example, commands to launch various applications or to log out.
Window manager menus in Linux are typically configurable either by editing text files, by using a desktop-environment-specific Control Panel applet, or both.
Amiga[edit]
The menu bar of AmigaOS 3.1 in its default state, showing the screen title. Shown here is the Workbench screen, which displays system information in its title.
The menu bar of AmigaOS 3.1 in its opened state. Holding the right mouse button down opens the menus in the menu bar, and releasing the button over a menu item selects that item. Each application can have its own separate menus.
The Amiga used a menu-bar style similar to that of the Macintosh, with the exception that the machine's custom graphics chips allowed each program to have its own 'screen', with its own resolution and colour settings, which could be dragged down to reveal the screens of other programs. The title/menu bar would typically sit at the top of the screen, and could be accessed by pressing the right mouse button, revealing the names of the various menus. When the right menu button was not pressed down, the menu/title bar would typically display the name of the program which owned the screen, and some other information such as the amount of memory used. When accessing menus with right mouse buttons pressed, one could select multiple menu entries by clicking the left mouse button, and when right mouse button was released, all actions selected in the menus would be performed in the order they were selected. This was known as multiselect.
The Workbench screen title bar would typically display the Workbench version and the amount of free Chip RAM and Fast RAM.[3] An unusual feature of the Amiga menu system was that the Workbench screen would display a 'Workbench' menu instead of a 'File' or 'Apple' menu, while conforming applications would display 'Project' and 'Tools' menus (projects and tools being, respectively, the Amiga terms for what in other systems are called files or documents, and programs or applications).
Keyboard shortcuts could be accessed by pressing the 'right Amiga' key along with a normal alphanumeric key.[4] (Some early keyboards had a Commodore key to the left of the spacebar instead of a 'left-Amiga' key.) The filled-in and hollowed-out designs, respectively, of the left- and right-Amiga (or Commodore and Amiga) keys are similar to the closed-Apple and open-Apple keys of Apple II keyboards.
NeXTstep[edit]
NeXTSTEP's menu implementation
The NeXTstep OS for the NeXT machines would display a 'menu palette', by default at the top left of the screen. Clicking on the entries in the menu list would display submenus of the commands in the menu. The contents of the menu change depending on whether the user is 'in' the Workspace Manager or an application. The menus and the sub-menus can easily be torn off and moved around the screen as individual palette windows.
Power users would often switch off the always-on menu, leaving it to be displayed at the mouse pointer's location when the right mouse button was pressed. The same implementation is used by GNUstep and conforming apps, though applications written for the host operating system or another toolkit will use the menu scheme appropriate to that OS or toolkit.
Atari TOS[edit]
The TOS operating system for the Atari ST would display menu bars at the top of the screen like Mac OS. Rather than being 'pulled-down' by holding the mouse button, the menu would appear as soon as the pointer was over its heading. This was done to get around an Apple patent on pull-down menus.
RISC OS[edit]
In RISC OS, clicking the middle button displays a menu list at the location of the mouse pointer. The RISC OS implementation of menus is similar to the context menus of other systems, except that menus will not close if the right mouse button is used to select a menu entry. This allows the user to implement or try out several settings before closing the menu.
Ease-of-use[edit]
In both Microsoft Windows and Apple Macintosh operating systems, in other similar desktop environments and in some applications, common functions are assigned keyboard shortcuts (e.g. Control-C or Command-C copies the current selection).
Microsoft-style bars are physically located in the same window as the content they are associated with. However, Bruce Tognazzini, former employee of Apple Inc. and Human–computer interaction professional, claims[5] that the Mac OS's menu bars can be accessed up to five times faster due to Fitts's law: because the menu bar lies on a screen edge, it effectively has an infinite height — Mac users can just 'throw' their mouse pointers toward the top of the screen with the assurance that it will never overshoot the menu bar and disappear.
This assumes that the desired menu is currently enabled, however. If another application has 'focus', the menu will belong to that application instead, requiring the user to check and see which menu is active before 'throwing' the mouse, and often perform an extra step of focusing the desired application before using the menu, which is completely separate from the application it controls. The effectiveness of this technique is also reduced on larger screens or with low mouse acceleration curves, especially due to the time required to travel back to a target in the window after using the menu.[6] On systems with multiple displays, the menu bar may either be displayed on a single 'main' display, or on all connected displays. The classic Mac OS, and versions of macOS prior to OS X Mavericks displayed only a single menu bar on the main display; Mavericks added the option to show the bar on all displays.
Menu Bar Stats 3 0 4
Some applications, e.g. Microsoft Office 2007, Internet Explorer 7 (by default), and Google Chrome and Mozilla Firefox 4 in Windows and Linux, have effectively removed the menu bar altogether by hiding it until a key is pressed (typically the 'alt' key). These applications present options to the user contextually, typically using hyperlinks to select actions.
See also[edit]
Menu Bar Stats 3 0 5
- IBM Common User Access – the standard that defined several aspects of menu layout commonly used by Windows and several Linux desktop environments today.
- Menu button – where a pop-up menu is beneath a button.
References[edit]
- ^http://www.folklore.org/images/Macintosh/polaroids/polaroids.14.jpg
- ^https://code.google.com/p/gnome2-globalmenu/
- ^Donner, Gregory S. 'Release 3.0'. Workbench Nostalgia: The history of the AmigaOS Graphic User Interface (GUI). Retrieved 2016-03-01.
- ^Commodore-Amiga, Incorporated (1991). 'The Keyboard'. Amiga User Interface Style Guide. Addison Wesley Publishing Company. p. 147. ISBN0-201-57757-7. Retrieved 2016-03-01.
Use a Right-Amiga combination as the default keyboard shortcut for a menu item.
- ^http://www.asktog.com/basics/firstPrinciples.html#fittsLaw
- ^http://lists.kde.org/?l=kde-look&m=95705988431395&w=2
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Menu_bar&oldid=983754232'
Developed by | Holger Wirtz Martin Spott Csaba Halasz Clément de l'Hamaide |
---|---|
Development status | Active |
License | GNU GPL v2 |
Website |
- 2FGCom Builtin
- 3FGCom standalone
- 4FAQ
- 4.1Related content
FGCom is a voice communication feature. That way you can communicate with other pilots and airspace controllers during your flight.
The main idea is to reproduce the real aviation communication, in other words this feature is designed to make radio communication as real as possible during your flights.
FGCom is available by two ways:
- Integrated into FlightGear (FGCom builtin): this is certainly the better solution because easier to use
- External software (FGCom standalone): you should use this one only if you plan to use FGCom in a special case
A web interface is available where you can see who is connected in live, the history, and statistics: http://fgcom.flightgear.org
IMPORTANT:
- FGCom builtin is available for FlightGear 3.0 or higher and is certainly the solution you are looking for because really easy to use.
- FGCom standalone is only for those who want a complex, yet more flexible, setup or don't use FlightGear 3.0 or higher.
- If you are not using FlightGear 3.0 or higher you have to read the FGCom standalone section and follow 'If FlightGear is not installed' instructions.
Installation
The good news here is that FlightGear has now an FGCom client built in the software. That means there is no additional installation step. If you have installed FlightGear you can immediately use FGCom.
How to start FGCom builtin ?
- Start FlightGear
- Open the dialog located in 'Multiplayer > FGCom Settings'
- Check the 'Enable' checkbox
- Close the dialog
You can also use the command line if you prefer:
FGCom will be automatically enabled for your future sessions until you uncheck the 'Enable' checkbox.
How to test your setup ?
In order to check that your microphone and speakers are correctly connected and functional you can test it with the following steps:
- Start FlightGear (if not yet done of course)
- Open the dialog located in 'Multiplayer > FGCom Settings'
- Check the 'Enabled' checkbox (If not yet already done.)
- Check the 'Display messages' checkbox. (Displays FGCom's messages on screen)
- Check the 'Echo test' checkbox
At this moment you should hear your own voice with a delay. If you can't hear your own voice it means your microphone or your speakers are wrongly set.
To further check your 'Echo test', see Live FGCom - Unckeck the 'Echo test' checkbox, and/or other boxes as desired.
- You can also check that your PTT works fine looking at the 'PTT test' checkbox when you press your PTT button (default is Space)
- Close the dialog
How to use FGCom builtin ?
Once you started FGCom from the How to start FGCom builtin procedure, you can simply use your radio stack like it done in real life.
When you want to talk you have to press Space. When the Space is pressed you can't hear other pilots.
You can switch between COM1 and COM2 by pressing ⇧ Shift + Space
FGCom dialog
NOTE: It maybe desirable to keep FGCom's Settings 'Display messages' activated, to verify these FGCom related keys are working properly.
Dialog details
The dialog located in 'Multiplayer > FGCom Settings' provide some features described here:
- Enable : you can check/uncheck this for enable/disable FGCom feature
- Display messages : display FGCom transaction message for debug only
- Echo test : check/uncheck this for testing server communication (Echo-Box)
- PTT test : when you press your PTT this checkbox will be checked
- Speaker volume : set speaker volume for FGCom built-in
- Silence threshold : set the limit, in dB, when FGCom consider no voice in your microphone
- Server > List : Select the server to be connected (immediat effect)
Installation
If FlightGear is installed:
The good news here is that if you have FlightGear installed on your computer you already have FGCom standalone!
If FlightGear is not installed:
If you haven't installed FlightGear on the computer where you want to use FGCom standalone you can simply download FGCom standalone with the following steps:
- Download FGCom standalone: Windows | Linux | Mac (take care to select the correct version for your computer!)
- Unzip the downloaded file
- That's all! Of course you can place the 'FGCom' folder where you want on your computer
On Linux, you have to setup the permission as 'executable' for the files 'run_fgcom.sh' and 'test_fgcom.sh'
How to start FGCom standalone ?
If FlightGear is installed:
On Windows you have to execute FGCom located in your Start menu > FlightGear > Tools > FGCom
On Linux you have to execute FGCom located in your Application menu > Games > FGCom
On Mac you have to enable 'Enable FGCOM in Multi Player mode' located in the tab 'Network' of the Mac launcher
If FlightGear is not installed:
On Windows, in your unzipped 'FGCom' folder, you have to execute (double clic on it) the file 'run_fgcom.bat'.
On Linux, in your unzipped 'FGCom' folder, you have to execute (double clic on it) the file 'run_fgcom.sh'.
On Mac, in your unzipped 'FGCom' folder, you have to execute (right-clic > open with > Terminal.app) the file 'run_fgcom.command'. After the first time you can simply double click on 'run_fgcom.command'.
In both case
Now a terminal has been opened and you should be able to see the following lines:
In order to stop FGCom standalone you have to press Control + c
How to test your setup ?
If FlightGear is installed:
On Windows you have to execute FGCom located in your Start menu > FlightGear > Tools > FGCom-testing
On Linux you have to execute FGCom located in your Application menu > Games > FGCom-testing
On Mac FIXME: require to be implemented in Mac launcher
If FlightGear is not installed:
On Windows, in your unzipped 'FGCom' folder, you have to execute (double clic on it) the file 'test_fgcom.bat'.
On Linux, in your unzipped 'FGCom' folder, you have to execute (double clic on it) the file 'test_fgcom.sh'.
On Mac, in your unzipped 'FGCom' folder, you have to execute (right-clic > open with > Terminal.app) the file 'test_fgcom.command'. After the first time you can simply double click on 'test_fgcom.command'.
In both case
Now you should be able to hear your own voice with a delay and see the following lines:
In order to stop FGCom standalone you have to press Control + c
How to use FGCom standalone ?
Once you started FGCom from the How to start FGCom standalone procedure, you have to start FlightGear with the following option:
Now you have to leave FGCom standalone running and simply use FlightGear without taking care of FGCom standalone.
When you want to talk you have to press Space. When the Space Wiso steuer: 2019 9 08 1932 grand prix. is pressed you can't hear other pilots.
You can switch between COM1 and COM2 by pressing ⇧ Shift + Space
You can control the sound volume with the slider 'ATC' from the File > Sound configuration dialog (even if ATC is unchecked)
During your FlightGear session you should be able to see some lines in the FGCom standalone, it's totally normal, they are here to inform you about the state of FGCom standalone (when you are listening, talking, changing frequency, changing COM1/2..)
In order to stop FGCom standalone you have to press Control + c or simply close the window.
Options details
Starting FGCom standalone with '--help' argument will show you all the available options.
IMPORTANT: Keep in mind that FGCom standalone works fine for a standard operating system without options at all ! Use them only if you know exactly what they do.
How to add the --generic option for FGCom standalone ?
![Stats Stats](https://pic.macw.com/pic/202002/21114236_9528d524c1.jpeg)
Since FlightGear 3.0 you can select 'FGCom standalone' in the FlightGear Launcher > Advanced > Network section else:
On the last page of the FlightGear Launcher, press 'Advanced' then select 'Input/Output' item. Press 'New' and set the fields as:
Menubar Stats 2
- Protocol : generic
- Medium : socket
- Direction : out
- Hz : 5
- Hostname : 127.0.0.1
- Port : 16661
- Select UDP
- Generic : fgcom
I want to use FGCom builtin but I haven't any item 'Multiplayer > FGCom Settings' in FlightGear
Because you are not using FlightGear 3.0 or higher. FGCom builtin is only available for FlightGear 3.0 or higher. You have to use FGCom standalone until you upgrade your FlightGear installation.
I want to use FGCom standalone but I haven't any FGCom item in 'Start menu > FlightGear > Tools'
Because you are not using FlightGear 3.0 or higher. FGCom standalone is automatically installed only for FlightGear 3.0 or higher.
You have to follow 'If FlightGear is not installed' instructions until you upgrade your FlightGear installation.
Receiptbox 2 2. I'm using FGCom standalone, other pilots can hear me but I can't hear other pilots
Menu Bar Stats 3 0 3
Be sure the slider 'ATC' from the File > Sound configuration dialog is at full right.
I'm using Linux and I can't get FGCom working
Please read this page which has a lot of information about audio configuration for Linux user, even some specific reference to FGCom: Linux software audio mixing with FlightGear
Related content
Wiki articles
Source code
Retrieved from 'http://wiki.flightgear.org/index.php?title=FGCom_3.0&oldid=128087'