Mall:Key press/doc Näita ajalugu

Resümee puudub
(All pages about Waze App have been obsoleted - wikilinks removal accordingly.)
1. rida: 1. rida:
{{Documentation subpage}}
Waze is a fun and sophisticated navigation app. In most developed countries Waze provides superior navigation information over commercial GPS applications. Like any developing application, there are issues and complications that are being worked to resolve. Many of them are cosmetic and do not prevent a fully gratifying experience when using Waze.
<!-- PLEASE ADD CATEGORIES AND INTERWIKIS LINKS AT THE END OF THIS PAGE. -->
__NOTOC__


This is the {{tl|key press}} template primarily designed to illustrate keys and keystrokes on a computer keyboard. With additional parameters, a single template can even illustrate a combination of multiple ''simultaneous'' keystrokes. A sequence of keystrokes, on the other hand, need to be demonstrated with separate templates.
Temporary issues are tracked in the official [http://status.waze.com/ Waze server status and issues] page.


Example:
Note that Waze Bugzilla, a tool previously used for bug reporting, is no longer in use. The Waze community used to report and tracks bugs and problems in the Bugzilla application. At the time, it was the best place to identify any currently known issues. There is no official replacement for Bugzilla.
:{{tlc|key press|A}} → {{key press|A}}


=== Keystroke combinations ===
Some of the more common issues include:
* Routing distance is limited to about 1,000 miles (1600 km) distance. To route to longer distances, select a point between your origin and destination less than this limit.


To illustrate keystroke combinations, just use extra parameters:
* When you request a route the client device app assumes you are continuing in the same direction you last traveled. This is often desirable, but can lead to unnecessarily longer routes when you have a choice of direction from your starting position. If you start driving the other direction, it will recalculate the route.
:{{tlc|key press|Alt|P}} → {{key press|Alt|P}}
:{{tlc|key press|Ctrl|Alt|Del}} → {{key press|Ctrl|Alt|Del}}


This template currently handles up to 10 key name parameters, which should be more than enough to accommodate for any possible combination of simultaneous keystrokes. If it gets too many key name parameters it reports the page into [[:Category:Keypress template parameter needs fixing]]. This means we can easily find those pages and fix them, or we can discover if we need to make this template take more parameters.
* Issues and limitations on your supported model smartphone


When you feed several key names to this template, it adds a "+" (or whatever the contents of the optional ''chain'' parameter) with no spaces around. This means it won't line wrap. But when you show key combinations for instance in a table then that might cause too wide items. Then instead manually build the key combination with spaces around the "+" so it can line wrap:
* Odd routing: Waze has been known to make short detours. In these situation, Waze instructs the driver to turn off a road, only to have the driver immediately return to it. Ostensibly, this shortens the route, but it produces routes that many drivers consider unreasonable, and the time savings are often dubious. Editors can often work around this using the [[Detour prevention]] mechanisms.
:{{tlc|key press|Ctrl}} + {{tlc|key press|Alt}} + {{tlc|key press|Del}} →
::{{key press|Ctrl}} + {{key press|Alt}} + {{key press|Del}}
:{{tlc|key press|Ctrl|Alt|Del|5=chain=&amp;#32;+&amp;#32;}} →
::{{key press|Ctrl|Alt|Del|chain=&#32;+&#32;}}


On the other hand, to illustrate Windows [[Alt code]]s you might want to use separate templates with no intervening punctuation or space. In most Windows systems in North America and Western Europe, for example, the [[plus-minus sign]] (±) can be entered by holding down the Alt key while typing <code>0177</code> (with the [[numeric keypad]]):
:{{tlc|key press|Alt|0}}{{tlc|key press|1}}{{tlc|key press|7}}{{tlc|key press|7}} →
::{{key press|Alt|0}}{{key press|1}}{{key press|7}}{{key press|7}}


An example of a use case where more than 5 might be used is explaining usage of a macro (keyboard shortcut) created by a third-party application:
<!-- do not include this template when transcluded -->
:{{tlc|Key press|Ctrl|Alt|Shift|Win|Menu|fn|L}} →
<noinclude>[[Category:Review Purpose]]</noinclude>
::{{Key press|Ctrl|Alt|Shift|Win|Menu|fn|L}}
 
=== Wikilinks ===
 
If there is an article about the key you can wikilink the key's name like any other wiki text. Like this:
* {{tlc|key press|<nowiki>[[Alt key|Alt]]</nowiki>}} → {{key press|[[Alt key|Alt]]}}
 
If you are wikilinking the keys, please ensure that you are piping to the correct page (e.g. <code><nowiki>[[Control key|Ctrl]]</nowiki></code> instead of <code><nowiki>[[Ctrl]]</nowiki></code>, which leads to a [[WP:Disambiguation page|disambiguation page]]).
 
=== Wiki markup characters ===
 
Some wiki markup character, like the [[pipe symbol]], the [[semicolon]] and the [[equals sign]], need to be entered using the {{tl|!}}, {{tl|;}} and {{tl|{{=}}}} templates or as an [[HTML entity]] &amp;#124;, &amp;#59;, &amp;#61; respectively:
* {{tlc|key press|{{Tlc|!}}}} → {{key press|{{!}}}}
* {{tlc|key press|&amp;#124;}} → {{key press|&#124;}}
* {{tlc|key press|{{Tlc|&#59;}}}} → {{key press|{{;}}}}
* {{tlc|key press|&amp;#59;}} →  {{key press|&#59;}}
* {{tlc|key press|{{Tlc|&#61;}}}} → {{key press|{{=}}}}
* {{tlc|key press|&amp;#61;}} →  {{key press|&#61;}}
 
However, if the characters are marked as wikilinks, they can be entered as such:
* {{tlc|key press|<nowiki>[[&#124;]]</nowiki>}} → {{key press|[[|]]}}
* {{tlc|key press|<nowiki>[[;]]</nowiki>}} → {{key press|[[;]]}}
* {{tlc|key press|<nowiki>[[=]]</nowiki>}} → {{key press|[[=]]}}
 
Most markup characters also have aliases:
* {{tlc|key press|pipe}} → {{key press|pipe}}
* {{tlc|key press|semicolon}} → {{key press|semicolon}}
* {{tlc|key press|equals}} → {{key press|equals}}
* {{tlc|key press|colon}} → {{key press|colon}}
* {{tlc|key press|asterisk}} → {{key press|asterisk}}
* {{tlc|key press|hash}} → {{key press|hash}}
 
=== Key symbols ===
 
Some key names have a fitting [[Unicode]] character. This template automatically adds such "icons" to the following key names among others (see also ''Arrows exception'' below).
* {{tlc|key press|Shift}} → {{key press|Shift}}
* {{tlc|key press|Tab}} → {{key press|Tab}}
* {{tlc|key press|Enter}} → {{key press|Enter}}
* {{tlc|key press|Option}} → {{key press|Option}}
* {{tlc|key press|Opt}} → {{key press|Opt}}
* {{tlc|key press|Command}} → {{key press|Command}}
* {{tlc|key press|Cmd}} → {{key press|Cmd}}
* {{tlc|key press|Caps Lock}} → {{key press|Caps Lock}}
* {{tlc|key press|Scroll Lock}} → {{key press|Scroll Lock}}
* {{tlc|key press|Up}} → {{key press|Up}}
* {{tlc|key press|Down}} → {{key press|Down}}
* {{tlc|key press|Left}} → {{key press|Left}}
* {{tlc|key press|Right}} → {{key press|Right}}
[[File:AltGr Win Menu Ctrl key.jpg|thumb|200px|Windows key and Menu key]]
[[File:Ctl wndws alt.jpg|thumb|200px|Old-style Windows key]]
There are no characters for the [[Windows key]] and [[Menu key]]. Besides, the Windows logo is trademarked. So this template shows approximate characters for them in the following way:
* {{tlc|key press|Win}} → {{key press|Win}}
* {{tlc|key press|Menu}} → {{key press|Menu}}
 
<!-- This is for other keyboard systems as it existed in Wikipedia; kept for reference only
==== Video games ====
 
Video game controllers often have specialized input labels that do not map easily. The following are mappings for various game consoles and input features.
 
===== Directional input =====
 
The following should only be used when the input sequence uses something other than the primary input or mixes input between directional devices.
 
* {{tlc|key press|l-down}} → {{key press|l-down}}
* {{tlc|key press|c-left}} → {{key press|c-left}}
* {{tlc|key press|r-up}} → {{key press|r-up}}
 
Stick specific diagonals are also supported:
 
* {{tlc|key press|l-nw}} → {{key press|l-nw}}
* {{tlc|key press|c-se}} → {{key press|c-se}}
* {{tlc|key press|r-ne}} → {{key press|r-ne}}
 
===== PlayStation =====
 
* {{tlc|key press|ex}} → {{key press|ex}}
* {{tlc|key press|circle}} → {{key press|circle}}
* {{tlc|key press|triangle}} → {{key press|triangle}}
* {{tlc|key press|square}} → {{key press|square}}
-->
{{clear}}
 
=== Technical details ===
 
This template calls {{tl|key press/core}}, which holds the code that otherwise would be repeated several times in {{tl|key press}}, thus simplifying the code.
 
=== TemplateData ===
 
{{TemplateDataHeader}}
<templatedata>
{
"description": "Illustrates keys and keystrokes on a computer keyboard. Keys can include: Ctrl, Alt, Del, Opt, Menu, Left etc. console keys: ex, circle, triangle, square, and left right and center analog sticks: l-down, c-left, r-ne. The names are case insensitive.",
"params": {
"1": {
"label": "First key",
"description": "First key",
"type": "string/line",
"required": true
},
"2": {
"label": "Second key",
"description": "Optional key press in combination as the first.",
"type": "string/line",
"required": false
},
"3": {
"label": "Third key",
"inherits": "2"
},
"4": {
"label": "Forth key",
"inherits": "2"
},
"5": {
"label": "Fifth key",
"inherits": "2"
},
"6": {
"label": "Sixth key",
"inherits": "2"
},
"7": {
"label": "Seventh key",
"inherits": "2"
},
"8": {
"label": "Eighth key",
"inherits": "2"
},
"9": {
"label": "Ninth key",
"inherits": "2"
},
"10": {
"label": "Tenth key",
"inherits": "2"
},
"chain": {
"label": "Chaining character",
"description": "Character between chained key presses",
"default": "+",
"inherits": "2"
},
"chain first": {
"description": "Character between first and second key to press",
"inherits": "chain"
},
"chain second": {
"description": "Character between second and third key to press",
"inherits": "chain"
},
"chain third": {
"description": "Character between third and fourth key to press",
"inherits": "chain"
},
"chain fourth": {
"description": "Character between fourth and fifth key to press",
"inherits": "chain"
}
}
}
</templatedata>
 
==== Not to be confused with ====
* {{tl|Button}} – Produces a similar visual effect, but without the semantic markup, e.g. {{Button|sample text}}.
 
<includeonly>
 
<!-- CATEGORY LINKS HERE, THANKS -->
 
[[Category:Programming typing-aid templates]]
<!-- [[Category:Graphic templates]] - Don't add this one; this isn't a graphic template, as it's all done in CSS. -->
[[Category:Semantic markup templates]]
[[Category:Computer keys]]
[[Category:Incomplete templates]]
 
</includeonly>

Redaktsioon: 1. aprill 2015, kell 09:14

Waze is a fun and sophisticated navigation app. In most developed countries Waze provides superior navigation information over commercial GPS applications. Like any developing application, there are issues and complications that are being worked to resolve. Many of them are cosmetic and do not prevent a fully gratifying experience when using Waze.

Temporary issues are tracked in the official Waze server status and issues page.

Note that Waze Bugzilla, a tool previously used for bug reporting, is no longer in use. The Waze community used to report and tracks bugs and problems in the Bugzilla application. At the time, it was the best place to identify any currently known issues. There is no official replacement for Bugzilla.

Some of the more common issues include:

  • Routing distance is limited to about 1,000 miles (1600 km) distance. To route to longer distances, select a point between your origin and destination less than this limit.
  • When you request a route the client device app assumes you are continuing in the same direction you last traveled. This is often desirable, but can lead to unnecessarily longer routes when you have a choice of direction from your starting position. If you start driving the other direction, it will recalculate the route.
  • Issues and limitations on your supported model smartphone
  • Odd routing: Waze has been known to make short detours. In these situation, Waze instructs the driver to turn off a road, only to have the driver immediately return to it. Ostensibly, this shortens the route, but it produces routes that many drivers consider unreasonable, and the time savings are often dubious. Editors can often work around this using the Detour prevention mechanisms.