add limitation of lop~

Author: dromer

docs/02.getting_started.md

@@ -122,4 +122,5 @@ This list will be continuously epanded to document differences in object behavio
 * `[snapshot~]` does not respond within the same control flow as it executes in signal context. Its output happens on the next audio cycle, so additional care for this control flow needs to be taken into account if you depend on synchronous execution. It also doesn't accept `[set(` messages.
 * Certain filters are sensitive to ‘blowing up’ at very low or very high cutoff frequencies and/or resonances, due to the filter coefficients not being perfectly represented with a finite number of bits. While Pure data natively uses 64 bits, platforms like `OWL` and `Daisy`  that use 32 bit float are more sensitive to this. For example, the Pure data `[bp~]` filter is implemented with a biquad which is prone to fail or distort with cutoff frequencies less than around 200 Hz (at 48kHz sample rate).
 * Right inlet for table onset of `[tabread4~]` does not do anything.
+* Right inlet for `[lop~]` does not support signal input.
 * Heavy does not support multichannel connections.

docs/09.supported_vanilla_objects.md

@@ -154,7 +154,7 @@ Here is a list of [unsupported Pd objects](10.unsupported_vanilla_objects.md).
 | hip~ | |
 | inlet~ | |
 | line~ | |
-| lop~ | |
+| lop~ | right inlet does not support signals |
 | max~ | |
 | min~ | |
 | mtof~ | |