Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
purr-data
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jonathan Wilkes
purr-data
Commits
b7251304
Commit
b7251304
authored
9 years ago
by
Jonathan Wilkes
Browse files
Options
Downloads
Patches
Plain Diff
update todo
parent
48c48223
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
pd/nw/todo.txt
+0
-13
0 additions, 13 deletions
pd/nw/todo.txt
with
0 additions
and
13 deletions
pd/nw/todo.txt
+
0
−
13
View file @
b7251304
...
...
@@ -168,19 +168,6 @@ Everything else: (A [x] means we've fixed it)
[x] Instead of hardcoded gui_post colors, set a class (warning, error, etc.)
[ ] revisit the function for escaping double-quotes inside s_inter.c, see
if there's a cleaner way to do it
[ ] the socket reader has a buffer capped at 4096. This is plenty for most
purposes, but it may choke if the user tries to enter a humongous amount
of text inside, say, a message box. Pd Vanilla handles this by sending
every single character that's typed into the box as a separate message
(which of course causes other problems, like copy/paste potentially flood-
ing the socket and freezing Pd.) Here, I am sending as a single message
"stringforobj" with the msg/obj box contents as the arguments. If that
message ends up being bigger than 4096 Pd will truncate the message.
A solution would be to send the box contents in smaller chunks-- bigger
than single chars but smaller than 4096. This will complicate the
interface, but the chunks should get sent in sequence so it might not
be too bad.
[ ] don't implement tooltips until we have a single call to create an object
plus all xlets. That way we can add an arg or two for the name and dir
to find the help patch and get all descriptions in one go
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment