-
Notifications
You must be signed in to change notification settings - Fork 757
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"String".newTextWindow complaints #1238
Comments
Okay, I'll take a look. You don't need to post on sc-dev as well, btw. |
Signed-off-by: Scott Wilson <i@scottwilson.ca>
Fixed. |
thank you, will try asap. |
I think it's fine to query on sc-dev if you're not sure it's a bug or whatever, but once it moves to a github issue, keep the discussion here. Definitely don't duplicate what you post here, as that's just noise for all active devs, which means more to read, which means we're actually less likely to see it. As someone who works in a large bureaucratic organisation, believe me when I say information creep is really worth resisting. |
Tested and it works. |
Maybe it would be an idea to close down the dev-mailing list? Splitting the development-oriented issues over two forums creates some uncertainty who actually reads what... So the user-list would be the general supercollider forum that serves traditional "mailing-list" communication, and development oriented stuff could be focused on github... |
No, I disagree. The dev list is very useful for general discussion about dev stuff. Github issues are very useful because they provide an easy way to track bugs and specific discussion about solving them in a way that doesn't get lost (as bugs so often did in the old days). In short, they serve different purposes. My 2 cents, anyway.
Great! |
I wonder how many people actually use sc-dev only. Leading that kind of general dev-discussion on sc-users would also contribute to a spirit of more inclusivity/equality. But then it might appear intimidating to others, so well... not a big issue anyways, just another set of 2 cents :) |
returns a new text window, however, it also posts an error:
tested on
3.7alpha0 on OSX Mavericks
The text was updated successfully, but these errors were encountered: