|
Introduction to Microcontroller Programming * Course Index * Introduction * About the Author * About this Course * Feedback * Course Navigation * Quick Course Navigation * How to use this Course * Acronyms Used and Course Conventions About PICmicro Chips * What is a PICmicro? * Microcontrollers * Digital versus Analogue * Inputs and Outputs * Memory * Programming * 16F1937 Architecture Clocking Your PICmicro Devices * Introduction * The Clock Circuit * Clock Settings * Clock Confusion E-Blocks * Introduction to E-blocks * Using E-blocks * E-blocks Boards Flowcode Step By Step * Introduction to Flowcode * Basic Flowcode Functions * Digital Outputs * Digital Inputs * Basic Loops * The LCD Display * Binary Numbers * Decisions * Goto (Connection Point) * 7-Segment Displays * Software Macro * Strings and Memory * A Simple Hi-Fi PICmicro Projects * Introduction to PICmicro Projects * Construction Methods * Choosing a Power Source * Adding Inputs * Input Conditioning * Adding Outputs * Adding Drivers Labs * Introduction and Lesson Plan * 1. Output * 2. Delay * 3. Connection Point * 4. Calculations * 5. Loop * 6. Input * 7. Decision * 8. LCD * 9. Keypad * 10. Analogue + EEPROM * 11. Software Macro * 12. External Interrupt * 13. Timer Interrupt |
(:Summary:Contains the 'action' links (like Browse, Edit, History, etc.), placed at the top of the page, see site page actions:) (:comment This page can be somewhat complex to figure out the first time you see it. Its contents are documented at PmWiki.SitePageActions if you need help. :) * Print (:comment (:if group Site,SiteAdmin,Cookbook,Profiles,PmWiki*:) (:comment delete if and ifend to enable backlinks:) * %item rel=nofollow class=backlinks accesskey='$[ak_backlinks]'% [[{*$Name}?action=search&q=link={*$FullName} | $[Backlinks] ]] (:ifend:) :) * Login PmWiki /
Page specific variables(:Summary: PmWiki group header. Includes styles and trail.:) (:comment please leave the multiple style definitions concatenated as a single line. Linebreaks do appear in the output when the wiki is configured with linebreaks enabled -- thanks!:) (:comment included in PmWiki localisation headers and footers :) authors (intermediate)
(:nl:)
(:Summary: variables that are associated with pages:) (:Audience: authors (intermediate) :) This page describes the "variables" that are associated with pages. Page variables have the form @@{$''variable''}@@, and can be used in page markup or in certain formatting strings in PmWiki. For example, the markup " Note: Do not confuse these variables (set and used only in PmWiki pages) with PHP variables. Page variables can be read in PHP with the PageVar() function. Note that these variables do not necessarily exist in the PHP code, because they have to be determined for a specific page. (However, they are usable in FmtPageName strings.) There is also the form @@{''pagename''$''variable''}@@, which returns the value of the variable for another page. For example, " Default page variablesThe page variables defined for PmWiki are: -> -> -> In addition to the above, there are some page-invariant variables available through this markup: -> -> Special referencesSpecial referenced variables are used to specify the context of the variable when: * the variable is included into a destination (target) page * the variable is used in a sidebar, header, or footer. Prefixing the variable name with an asterisk (*) means the variable's value is related to the browsed page or main (body) page. * @@{''' -< See also For example you can test to see if the page is part of another page
Page variable security ($authpage)The form @@{''pagename''$''variable''}@@ or some PageLists, can display the values for other pages, regardless of the password protections. If the other pages are protected and the visitor has no read permissions, PageVariables, unlike PageTextVariables, normally display the values. While most variables do not contain sensitive information, some of them could do: $Title, $Description and those starting with $LastModified. Administrators and module developers can redefine the sensitive page variables to respect authentications, by using the "$authpage" variable instead of "$page" in the definition. The following snippet can be added in local/config.php -- it will rewrite the default possibly sensitive definitions to the secure ones.
foreach($FmtPV as $k=>$v) {
if(preg_match('/^\\$(Title(spaced)?|LastModified(By|Host|Summary|Time)?|Description)$/', $k))
$FmtPV[$k] = str_replace('$page', '$authpage', $v);
}
Custom page variablesYou may add custom page variables as a local customization. In a local configuration file or a recipe script, use the variable -> $FmtPV['$VarName'] = "'variable definition'"; $FmtPV['$CurrentSkin'] = '$GLOBALS["Skin"]'; $FmtPV['$WikiTitle'] = '$GLOBALS["WikiTitle"]'; Defines new Page Variable of name $CurrentSkin, which can be used in the page with You can make a string a Page Variable by adding the string to the $GLOBALS[] array first. ->
## Create a {$BaseUrl} page variable
$GLOBALS['BaseUrl'] = $UrlScheme."://".$_SERVER["HTTP_HOST"]."/Wiki";
$FmtPV['$BaseUrl'] = '$GLOBALS["BaseUrl"]';
You can also have a function create the string. ->
## Create a {$BaseUrl} page variable
function BaseUrl() {
global $UrlScheme;
return $UrlScheme."://".$_SERVER['HTTP_HOST']."/Wiki";
}
$FmtPV['$BaseUrl'] = 'BaseUrl()';
>>frame<<
Please note that the values of the elements of -> See the recipe Cookbook:HttpVariables for a better way to use these variables. >><< See also* Cookbook:More custom page variables * PmWiki.Variables — about variables internal to PmWiki. * PmWiki.MarkupMasterIndex — complete list of PmWiki markups. * PageTextVariables — page variables automatically made available through natural page markup or explicit page markup within the wiki text of the page. * PmWiki.Markup Expressions — markup expressions can manipulate page variables Q:Is there a variable like $LastModified, but which shows me the creation time? A:No, but you can create one in config.php. For instance: -> # add page variable {$PageCreationDate} in format yyyy-mm-dd
$FmtPV['$PageCreationDate'] = 'strftime("%Y-%m-%d", $page["ctime"])';
If you like the same format that you define in config.php with $FmtPV['$Created'] = "strftime(\$GLOBALS['TimeFmt'], \$page['ctime'])"; Q: How can I test if a variable is set and/or not empty? A: Use @@(:if ! equal "{$Variable}" "":) $Variable is not empty. (:ifend:)@@. Note that undefined/inexistent variables appear as empty ones. Categories: PmWiki Developer(:nl:)(:Summary:Trail and talk page links:) (:comment included in PmWiki localisation headers and footers :) <<? >>bgcolor=#ffe border-top="1px solid black" font-size=.8em<< This page may have a more recent version on pmwiki.org: PmWiki:PageVariables, and a talk page: PmWiki:PageVariables-Talk. >><< |
(:Summary: Website page footer:)
Print - (:comment (:if group Site,SiteAdmin,Cookbook,Profiles,PmWiki*:) (:comment delete if and ifend to enable backlinks:) %item rel=nofollow class=backlinks accesskey='$[ak_backlinks]'% [[{*$Name}?action=search&q=link={*$FullName} | $[Backlinks] ]] (:ifend:) :) Search - Login
Page last modified on October 01, 2018, at 06:02 AM