I kept getting an odd exception during my tests. It looks like Vue-3.0.0 can become confused when state watchers (created via Vue.$watch) are unregistered during a later stage of a component lifecycle - trying to remove item from `null`.
I fail to see the error in my code at least (which works fine in Vue-2) and suspect it's a genuine Vue bug, filed here:
Can we please, please – PLEASE! not make the nonsensical US date format month/day/year the default in applications? 🤦♂️
PRE 👏 TTY 👏 PLEASE
And to all users of that format: it makes no sense, it's counter-intuitive, it makes collaboration frustrating, it introduces inconsistencies and errors... Just stop. Please. Use international standards.
(And don't get me started on your other units of weights, volumes and distances. Bloody hell.)
Boost if I'm right.
Now I'm wondering if Pen + Eraser work better as piano roll cursors, or if it is better to always use a cross-hair + tool icon cursor, like #Gimp does it.
Some users want to intentionally disable that though...
@bugaevc If the allocation is big enough to be worth shrinking, it is big enough to be put on heap. ;-)
I'm working on a new knob for #Beast, with bidirectional and unidirectional modes.
Sadly, Chrome cannot compose *inside* and SVG, so I have some nasty splitting and layering of the #SVG elements going on...
Or, SysRq is useful for users with hanging Linux systems, in case of unrecoverable system lockups:
Use with caution, don't try at home, yada yada.
Despite the other SysRq functions, these are enabled by default.
3/3 While the ability to run at nice priority -20 still requires root permission for the initial setup (or SYS_CAP_NICE), even that could *potentially* change with the introduction of a latency nice setting, if the kernel developers manage to implement unelevated latency re-nicing without opening up the gates for DOS attacks.
These developments are described in the LWN article 'The many faces of "latency nice"':
2/3 Not only is the risk of system lockups unwarranted to avoid audio drop outs, there is also no need for it to be taken.
Just prioritizing the audio rendering threads to run at nice level -20 is sufficient to prevent drop outs in low-latency setups, i.e. setups with <10ms round trip time. BTW, such setups require audio fragment sizes <= 128 samples (or "periods with <= 128 frames" in ALSA language).
1/3 On the topic of Linux low-latency audio setups…
Installing jackd (1 or 2) still requests "realtime priority" to minimize latency.
This project should really get its act together and stop demanding this kind of elevation from benign audiophile users.
Resistance is fruitful: 😀
CANN rejects sale of .org registry to for-profit investor group
@sir Can't answer that without multiple choice.
@linuzifer front-end or back-end inserter?
@email@example.com See the #GNU coding standard, section "5.1 Formatting Your Source Code". Yes, grep-ability was one idea, but with C++ classes, grepping for function names starting in column 1 doesn't work as well as in C.
»Video: Wie wichtig Abstand halten ist, um andere nicht mit dem Coronavirus zu infizieren, zeigt ein faszinierendes Video.«
DSP + UI developer on the Beast DAW, Free Software author + advocate, contributor to ALSA/GNOME/procps/LibreOffice/etc.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!