<aname="l1"></a><spanclass=cF0>The editor mostly stays in a </span><ahref="https://zeal-operating-system.github.io/ZealOS/Kernel/SerialDev/Message.ZC.html#l170"><spanclass=cF4>KeyGet</span></a><spanclass=cF0>()/</span><ahref="https://zeal-operating-system.github.io/ZealOS/Kernel/KeyDev.ZC.html#l1"><spanclass=cF4>PutKey</span></a><spanclass=cF0>() loop. The putkey portion is where keys are acted-upon. ZealOS has a chain
<aname="l2"></a>of putkey handlers in a </span><spanclass=cF4><u>Circular Queue</u></span><spanclass=cF0> with priorities. The highest priority handlers can choose to terminate handling,
<aname="l3"></a>otherwise, the keys get sent on down the chain.
<aname="l5"></a></span><ahref="https://zeal-operating-system.github.io/ZealOS/Kernel/KeyDev.ZC.html#l81"><spanclass=cF4>KeyDevAdd</span></a><spanclass=cF0>() defines a putkey device with a priority. "Device" might be a misnomer. Currently, the following are defined:
<aname="l9"></a></span><spanclass=cF2>0x20000000</span><spanclass=cF0></span><ahref="https://zeal-operating-system.github.io/ZealOS/Home/HomeKeyPlugIns.ZC.html#l11"><spanclass=cF4>MyPutKey</span></a><spanclass=cF0>() user handler
<aname="l10"></a></span><spanclass=cF2>0x40000000</span><spanclass=cF0></span><ahref="https://zeal-operating-system.github.io/ZealOS/Kernel/KeyDev.ZC.html#l124"><spanclass=cF4>KDInputFilterPutKey</span></a><spanclass=cF0>() for </span><ahref="https://zeal-operating-system.github.io/ZealOS/Kernel/Job.ZC.html#l580"><spanclass=cF4>In</span></a><spanclass=cF0>(), </span><ahref="https://zeal-operating-system.github.io/ZealOS/Kernel/Job.ZC.html#l561"><spanclass=cF4>InStr</span></a><spanclass=cF0>(), and </span><ahref="https://zeal-operating-system.github.io/ZealOS/Kernel/Job.ZC.html#l572"><spanclass=cF4>InFile</span></a><spanclass=cF0>() handling.
<aname="l11"></a></span><spanclass=cF2>0x60000000</span><spanclass=cF0></span><ahref="https://zeal-operating-system.github.io/ZealOS/Kernel/KeyDev.ZC.html#l99"><spanclass=cF4>KDRawPutKey</span></a><spanclass=cF0>() nonwindowed direct to video mem debug output.
<aname="l12"></a></span><spanclass=cF2>0x80000000</span><spanclass=cF0></span><ahref="https://zeal-operating-system.github.io/ZealOS/System/DolDoc/DocPutKey.ZC.html#l948"><spanclass=cF4>KDDocPutKey</span></a><spanclass=cF0>() standard document cmds
<aname="l17"></a></span><ahref="https://zeal-operating-system.github.io/ZealOS/Kernel/KernelA.HH.html#l1502"><spanclass=cF4>CDoc</span></a><spanclass=cF2>.user_put_key</span><spanclass=cF0> and </span><ahref="https://zeal-operating-system.github.io/ZealOS/Kernel/KernelA.HH.html#l1502"><spanclass=cF4>CDoc</span></a><spanclass=cF2>.user_put_s</span><spanclass=cF0> are call back routines which offer some neat tricks. See </span><ahref="https://zeal-operating-system.github.io/ZealOS/Apps/Psalmody/JukeBox.ZC.html#l1"><spanclass=cF4>::/Apps/Psalmody/JukeBox.ZC</span></a><spanclass=cF0>.
<aname="l18"></a>There is a variable </span><ahref="https://zeal-operating-system.github.io/ZealOS/Kernel/KernelA.HH.html#l1502"><spanclass=cF4>CDoc</span></a><spanclass=cF2>.user_put_data</span><spanclass=cF0> which gets passed to them.