I'm not really a windows user, but given the latest discussion on the rust subreddit, I thought I give using gtk4-rs on windows a try.
To set up my build environment, I followed this blog post:
That way, I successfully built and installed gtk4/master. And I can launch gtk4-demo.
Building from the tag 4.3.0 didn't work for me, as the source of glib couldn't be checked out.
In the blog above, things got installed to C:\GNOME. I chose C:\GTK instead, but the name doesn't really matter.
| #!/usr/bin/env python | |
| # | |
| # Based on a script by Donald Feury | |
| # https://gitlab.com/dak425/scripts/-/blob/master/trim_silenceV2 | |
| # https://youtu.be/ak52RXKfDw8 | |
| import math | |
| import sys | |
| import subprocess | |
| import os |
| /** | |
| * https://github.com/GoogleChromeLabs/comlink/blob/master/docs/examples/06-node-example/main.mjs | |
| * https://github.com/GoogleChromeLabs/comlink/issues/476#issuecomment-642765445 | |
| * esModuleInterop to true in tsconfig.json compilerOptions. | |
| */ | |
| import { Worker } from 'worker_threads'; | |
| import * as comlink from 'comlink'; | |
| import nodeEndpoint from 'comlink/dist/umd/node-adapter'; | |
| import { cpus } from 'os'; |
Peter Naur's classic 1985 essay "Programming as Theory Building" argues that a program is not its source code. A program is a shared mental construct (he uses the word theory) that lives in the minds of the people who work on it. If you lose the people, you lose the program. The code is merely a written representation of the program, and it's lossy, so you can't reconstruct
| How to fix a corrupt zsh history file | |
| Occasionally you may find you have a corrupt zsh history file preventing you from using the `fc` command or searching the history. Here's how to fix it. | |
| Estimated reading time: 1 minutes | |
| Table of contents | |
| Corrupt ZSH history file | |
| How to fix it | |
| Making it a script | |
| Corrupt ZSH history file | |
| If you use zsh for your shell very occasionally you may find the following message appearing indicating a corrupt history file. This is normally after a reboot. |
| export default function useAbortableAsyncCallback(callback, inputs) { | |
| const abortHandleRef = useRef(); | |
| const runAbortHandle = useCallback(() => { | |
| if (abortHandleRef.current) { | |
| abortHandleRef.current(); | |
| } | |
| }, []); |
Andy Thomason is a Senior Programmer at Genomics PLC. He has been witing graphics systems, games and compilers since the '70s and specialises in code performance.
| #!/usr/bin/env python | |
| import re | |
| import gzip | |
| import argparse | |
| from collections import defaultdict | |
| class Alignment: | |
| def __init__(self, in_r_start, in_r_end, in_q_start, in_q_end, in_cigar, in_strand, in_num_matches, in_aln_len, in_num_mismatches): |
