A common protocol structure is to have a header containing a length field, followed by data of length bytes, followed by additional protocol fields such as a CRC. If the length field is variable, the position of subsequent URH-specified protocol fields defined by fixed position will not be in the correct location.

I do not know the best way to address this, but quick and easy way to support

The new interface has the ability to create flow graphs of unlimited size by adaptive canvas expanding. However, the canvas can't expand to the left or up, and there is no "overshoot protection" for blocks being moved beyond the left or top boundary. This leads to losing access to the block groups which have been moved too far because the screen can not scroll to them being visible. I want to dele