![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
eubI haven't made a habit of posting daily, or with the intent of just logging what happened. But with all of the unstructured time I've got these days, I find myself wondering "what did I do all of this week?". So for a while I'll try logging what I did each day, so I can look back and see if I like in the aggregate how I'm spending my time. When you see an lj-cut text="day dump" , that's what's behind it. Day dumps are in general not going to be interesting to read.
today mostly frotzing with oedhack (a program to alter the UI of the OED software to my liking). the MessageBox popups I'm using to printf from the message hook may be interfering with message receipt and giving me this weird behavior. better to printf through IPC to a console pane on the hookmaster app.
a pipe seems nice. create it in the hookmaster and poke the write handle into the hook dll. but when the hook fires, it sees the handle == 0.
figured out that two processes' instantiation of a dll do not share its data. easiest way to make them share is #pragma data_seg(".myseg") and a SHARED directive to the linker.
linker can't find myseg. myseg doesn't show up in the .map file. fucking fuck SO B0RKEN. secret: data in myseg has to be initialized, or it gets dumped in BSS.
pipe write handle is still "invalid". do pipes maybe only work between related processes? that would be silly. maybe I should see if named pipes work any better here.
talked to my mom for a while. got Oliver first; he's home for the weekend, has his license but hasn't driven on it, and needs to decide in the next couple of weeks where to apply early decision.
picked up Dee.
oedhack. intended to replace the pipe code with named pipes. decided to use version control. decided to learn perforce, downloaded, played with, confused it by editing client definitions out from under it, bleh. tried two clients, conflict resolution.
time to pick a new book and go read.
[hmm. dial the detail way down.]
today mostly frotzing with oedhack (a program to alter the UI of the OED software to my liking). the MessageBox popups I'm using to printf from the message hook may be interfering with message receipt and giving me this weird behavior. better to printf through IPC to a console pane on the hookmaster app.
a pipe seems nice. create it in the hookmaster and poke the write handle into the hook dll. but when the hook fires, it sees the handle == 0.
figured out that two processes' instantiation of a dll do not share its data. easiest way to make them share is #pragma data_seg(".myseg") and a SHARED directive to the linker.
linker can't find myseg. myseg doesn't show up in the .map file. fucking fuck SO B0RKEN. secret: data in myseg has to be initialized, or it gets dumped in BSS.
pipe write handle is still "invalid". do pipes maybe only work between related processes? that would be silly. maybe I should see if named pipes work any better here.
talked to my mom for a while. got Oliver first; he's home for the weekend, has his license but hasn't driven on it, and needs to decide in the next couple of weeks where to apply early decision.
picked up Dee.
oedhack. intended to replace the pipe code with named pipes. decided to use version control. decided to learn perforce, downloaded, played with, confused it by editing client definitions out from under it, bleh. tried two clients, conflict resolution.
time to pick a new book and go read.
[hmm. dial the detail way down.]
