aboutsummaryrefslogtreecommitdiffstats
path: root/mode-button-event
diff options
context:
space:
mode:
authorGravatar Christian Hesse <mail@eworm.de>2019-01-03 17:45:43 +0100
committerGravatar Christian Hesse <mail@eworm.de>2019-01-04 12:35:34 +0100
commit870f00bb36f5af3088344371764da48bbde9651a (patch)
tree4e41839d17515cf05cb563fbb4dee92970889941 /mode-button-event
parent7d06a7e8c2b66a12db65130bddb3578b3f04468f (diff)
downloadrouteros-scripts-870f00bb36f5af3088344371764da48bbde9651a.tar.gz
routeros-scripts-870f00bb36f5af3088344371764da48bbde9651a.tar.zst
global: variable names are CamelCase
___ _ ___ __ / _ )(_)__ _ / _/__ _/ /_ / _ / / _ `/ / _/ _ `/ __/ /____/_/\_, / /_/ \_,_/\__/ _ __ /___/ _ __ | | / /___ __________ (_)___ ____ _/ / | | /| / / __ `/ ___/ __ \/ / __ \/ __ `/ / | |/ |/ / /_/ / / / / / / / / / / /_/ /_/ |__/|__/\__,_/_/ /_/ /_/_/_/ /_/\__, (_) /____/ RouterOS has some odd behavior when it comes to variable names. Let's have a look at the interfaces: [admin@MikroTik] > / interface print where name=en1 Flags: D - dynamic, X - disabled, R - running, S - slave # NAME TYPE ACTUAL-MTU L2MTU 0 RS en1 ether 1500 1598 That looks ok. Now we use a script: { :local interface "en1"; / interface print where name=$interface; } And the result... [admin@MikroTik] > { :local interface "en1"; {... / interface print where name=$interface; } Flags: D - dynamic, X - disabled, R - running, S - slave # NAME TYPE ACTUAL-MTU L2MTU 0 RS en1 ether 1500 1598 ... still looks ok. We make a little modification to the script: { :local name "en1"; / interface print where name=$name; } And the result: [admin@MikroTik] > { :local name "en1"; {... / interface print where name=$name; } Flags: D - dynamic, X - disabled, R - running, S - slave # NAME TYPE ACTUAL-MTU L2MTU 0 RS en1 ether 1500 1598 1 S en2 ether 1500 1598 2 S en3 ether 1500 1598 3 S en4 ether 1500 1598 4 S en5 ether 1500 1598 5 R br-local bridge 1500 1598 Ups! The filter has no effect! That happens whenever the variable name ($name) matches the property name (name=). And another modification: { :local type "en1"; / interface print where name=$type; } And the result: [admin@MikroTik] > { :local type "en1"; {... / interface print where name=$type; } Flags: D - dynamic, X - disabled, R - running, S - slave # NAME TYPE ACTUAL-MTU L2MTU Ups! Nothing? Even if the variable name ($type) matches whatever property name (type=) things go wrong. The answer from MikroTik support (in Ticket#2019010222000454): > This is how scripting works in RouterOS and we will not fix it. To get around this we use variable names in CamelCase. Let's hope Mikrotik never ever introduces property names in CamelCase... *fingers crossed*
Diffstat (limited to 'mode-button-event')
-rw-r--r--mode-button-event10
1 files changed, 5 insertions, 5 deletions
diff --git a/mode-button-event b/mode-button-event
index 8428945..82c1f4b 100644
--- a/mode-button-event
+++ b/mode-button-event
@@ -4,16 +4,16 @@
#
# run on mode-button event and count button presses
-:global "mode-button";
+:global ModeButton;
-:set ($"mode-button"->"count") ($"mode-button"->"count" + 1);
+:set ($ModeButton->"count") ($ModeButton->"count" + 1);
-:local scheduler [ / system scheduler find where name="mode-button-scheduler" ];
+:local Scheduler [ / system scheduler find where name="mode-button-scheduler" ];
-:if ([ :len $scheduler ] = 0) do={
+:if ([ :len $Scheduler ] = 0) do={
:log info "Creating mode-button scheduler, counting presses...";
/ system scheduler add name=mode-button-scheduler on-event=mode-button-scheduler interval=3s;
} else={
:log debug "Updating mode-button-scheduler...";
- / system scheduler set $scheduler start-time=[ /system clock get time ];
+ / system scheduler set $Scheduler start-time=[ /system clock get time ];
}