Jonathan Wilkes (92eef59d) at 10 Mar 22:35
add another project idea wrt LLMs
Jonathan Wilkes (dee66524) at 12 Feb 21:11
add vanilla compatibility project to large size list as well
... and 1 more commit
Jonathan Wilkes (9bde89da) at 12 Feb 21:02
Merge branch 'summer-of-code-ideas-list-ag-ideas'
... and 2 more commits
Jonathan Wilkes (1dd87661) at 11 Feb 21:46
add 90 hour ideas
Jonathan Wilkes (54569661) at 06 Feb 06:10
update ideas for 2024, document Brittney's completed project from 2023
This even happens if the delay for the timer is set to a really large value like 5000.
This doesn't make sense to me. Are you really waiting 5 seconds before the recovery prompt begins to block in javascript? If so, how is that different than opening a "message" dialog? I don't understand how one makes the backend bail and the other is fine...
microsleep select: Interrupted system call
in s_inter.c line 224:
if (select(sys_maxfd+1, &readset, &writeset, &exceptset, &timout) < 0)
perror("microsleep select");
So I'm guessing microsleep is whirring and then gets a signal that the GUI side of the socket got closed? Again, perhaps the dialog is preempting some initialization.
@jwilkes, I'm out of my depth here, can you help with this?
It sounds like when the prompt gets created, we haven't fully initialized the GUI <-> Pd communication yet. Are we sure the socket connection has been set up by this point?
For a sanity check, you can try using the shortcut <ctrl-m>
to pop up the message-sending dialog that blocks the GUI. I can create one of those in both the main Pd window or a patch window and leave them there without causing problems. I can even create one in the middle of populating a patch and things will resume fine when I close it. Once Purr GUI and backend are properly initialized the blocking modal window shouldn't be an issue.
Thanks for merging the previous MRs!
This just bumps the version number and removes some obsolete notes about Gem not being available on Mac in the help browser.
Once you merge this, our repos will be in sync again, so that I can go ahead and tag the final 2.19.3 release on GH (this is only available as a pre-release right now).
Jonathan Wilkes (50241ace) at 25 Jul 21:39
Merge branch 'purr-data-2.19.3-release'
... and 3 more commits
Jonathan Wilkes (05c673a0) at 19 Jul 02:49
Merge branch 'purr-data-pd-lua-update'
... and 1 more commit
Updated some outdated information, removed some L2ork branding, fixed some typos and formatting glitches.
Jonathan Wilkes (01cad508) at 19 Jul 02:48
Merge branch 'purr-data-update-readme'
... and 2 more commits
This fixes some glitches in our API to improve compatibility with vanilla. Specifically:
Added the missing obj_findsignalscalar declaration to m_imp.h.
Purr Data's glist_grab function has an extra argument, so I renamed it to glist_grabx and provided a vanilla-compatible glist_grab function that can be used by bundled and 3rd party externals. There are precisely two instances in g_numbox.c and g_text.c where the extra argument is actually needed, these use glist_grabx now. While I was at it, I also fixed a bug in g_numbox.c related to glist_grabx and slashed some gcc warnings in src/pd.
I also removed some public class definitions from g_canvas.h which might clash with 3rd party externals (ELSE, in particular). Checking for these classes is all the functionality needed across the internals, so I provided suitable predicate functions instead.
With this, I can now build Alexandre's ELSE against Purr Data. Here's a screenshot which shows one of ELSE's help patches purring happily.
So in principle adding ELSE to purr-data/externals as a submodule and building it in externals/Makefile will be as easy as pie now. I can submit another MR for that if wanted. But there still are two roadblocks on that avenue:
Jonathan Wilkes (fe7c2e72) at 19 Jul 02:47
Merge branch 'purr-data-vanilla-compatibility-fixes'
... and 12 more commits
Your screenshot looks fine, but for some reason I cannot fetch the branch from your fork. Did you delete it?
Something seems to be wrong-- I cannot view or fetch your branch.
Jonathan Wilkes (d79195a2) at 05 Mar 21:43
remove old initialization code