Aliaksei Chapyzhenka
Aliaksei Chapyzhenka
@Remillard will this work? ``` {signal: [ {name: 'sclk', wave: 'l.P.|.', phase: .5}, {name: 'sdmosi', wave: '0222', data: 'WR A14 A13 A12'}, ]} ``` 
I agree that is it ugly. The gap on the left is because nothing defined to the left of the first 0 in your `wave`. The waveform is constructed from...
yes, if you use `config:{skin:'narrow'}` and `period: 2` you can use granularity 0.5 `period: 4` you can use granularity 0.25
Please add a test for this change.
This is the best set of examples right now https://observablehq.com/collection/@drom/bitfield
yes, that is a bug. Will the timeout work when the main JS thread is blocked by an infinite loop? Or we better run this code in a web worker?
You need to find and delete NWJS local storage. Here are related threads: * https://stackoverflow.com/questions/66018792/nw-js-local-storage-cache-still-persists-even-after-app-uninstallation * https://stackoverflow.com/questions/33880506/chrome-local-storage-deleting-after-nwjs-application-closes-on-windows
@tudortimi duplicate of: https://github.com/drom/wavedrom/issues/48
We have new syntax for multi-cycle bricks that we can probably use: ``` { signal: [ { name: 'clk' }, { name: 'addr', wave: 'x==.', data: 'A0'} ]} ``` But...
@tudortimi @itsayellow Yes, `` is sub-cycle tag, giving one brick per character with any period. I have bumped wavedrom and online editor with related fixes. Please try: ``` { signal:...