From b72513041259b2280818cdcb634176dc92c7af2c Mon Sep 17 00:00:00 2001
From: Jonathan Wilkes <jon.w.wilkes@gmail.com>
Date: Tue, 26 Jan 2016 16:17:02 -0500
Subject: [PATCH] update todo
---
pd/nw/todo.txt | 13 -------------
1 file changed, 13 deletions(-)
diff --git a/pd/nw/todo.txt b/pd/nw/todo.txt
index 55960b260..ae3a909fc 100644
--- a/pd/nw/todo.txt
+++ b/pd/nw/todo.txt
@@ -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
--
GitLab