Max 6 issues - Revision history

Amounra: /* general */

2012-07-03T19:08:06Z

‎general

Ground state: cafe

2012-07-01T15:59:25Z

cafe

Ground state: binary

2012-07-01T15:53:52Z

binary

Amounra: /* aumboids */

2012-07-01T03:57:00Z

‎aumboids

Amounra: /* general */

2012-07-01T03:55:58Z

‎general

Amounra: /* tintinnabulome */

2012-07-01T03:51:21Z

‎tintinnabulome

Amounra: /* tintinnabulome */

2012-07-01T03:50:14Z

‎tintinnabulome

Ground state at 03:24, 1 July 2012

2012-07-01T03:24:15Z

Ground state at 02:47, 1 July 2012

2012-07-01T02:47:59Z

Ground state: page created

2012-07-01T02:47:39Z

page created

New page

It's possible that some of these '''aren't''' Max 6 related, but that's what I'm testing with, so...
aumboids says "#N: extra arguments for message "funnel""
presscafe: help goes to "Presscafe" rather than "PressCafe" (I've already made a redirect)

← Older revision		Revision as of 19:08, 3 July 2012
Line 65:		Line 65:

	'''This particular problem is due to the wrong initalization order, and may be due some change in the behavior of [live.this_device]. I'm hoping to finish up with current Max5 stuff tonight and switch to Max6 for testing of a project tomorrow before release, so hopefully I'll be able to catch up with what's going on.'''		'''This particular problem is due to the wrong initalization order, and may be due some change in the behavior of [live.this_device]. I'm hoping to finish up with current Max5 stuff tonight and switch to Max6 for testing of a project tomorrow before release, so hopefully I'll be able to catch up with what's going on.'''
		+
		+	'''Okay, I've had time to test this stuff with Max6 now, and I can say that all the connection routines were scrubbed by changes in Max6 with their API/JS implementation that they didn't bother to tell anyone about (not that I saw, anyway). I've got new versions in the works, hope to get them out for testing by the weekend.'''

← Older revision		Revision as of 15:59, 1 July 2012
Line 28:		Line 28:
	===== presscafe =====		===== presscafe =====
	help goes to "Presscafe" rather than "PressCafe" (I've already made a redirect)		help goes to "Presscafe" rather than "PressCafe" (I've already made a redirect)
		+
		+	Say... What '''is''' the difference between "cafe" and "presscafe"?

@@ Line 15: / Line 15: @@
 #N: extra arguments for message "funnel"</nowiki>
-This error is fixed in my working versions, and will be included in the next official package.
+'''This error is fixed in my working versions, and will be included in the next official package.'''
 ===== polygome =====
@@ Line 29: / Line 34: @@
 #N: extra arguments for message "s"</nowiki>
+'''Spent a total of about 3 hours trying to determine where that comes from over the last year....it drives me nuts.'''
-Spent a total of about 3 hours trying to determine where that comes from over the last year....it drives me nuts.
+'''It's an artifact from the original, I think, but I haven't been able to route it out.  I think its harmless.  - a'''
 ===== general =====
@@ Line 56: / Line 60: @@
 js: error calling function key</nowiki>
-These type of errors are what I'm mainly interested in:  they reflect how the mod.js and Python cores interact in Max6.  I'm currently working on b994 revs of these core scripts, so anything strange happening with connection routines or entering/exiting/saving from the editor are very noteworthy, and extrememly helpful.  It is because my implementation, by necessity, is so convoluted that I've delayed moving to Max6 for so long.
+'''This particular problem is due to the wrong initalization order, and may be due some change in the behavior of [live.this_device].  I'm hoping to finish up with current Max5 stuff tonight and switch to Max6 for testing of a project tomorrow before release, so hopefully I'll be able to catch up with what's going on.'''

← Older revision		Revision as of 03:57, 1 July 2012
Line 15:		Line 15:
	#N: extra arguments for message "funnel"</nowiki>		#N: extra arguments for message "funnel"</nowiki>

		+	This error is fixed in my working versions, and will be included in the next official package.

	===== polygome =====		===== polygome =====

← Older revision		Revision as of 03:55, 1 July 2012
Line 54:		Line 54:
	js: mod_b993.js: Javascript TypeError: stored_keys is undefined, line 441		js: mod_b993.js: Javascript TypeError: stored_keys is undefined, line 441
	js: error calling function key</nowiki>		js: error calling function key</nowiki>
		+
		+
		+	These type of errors are what I'm mainly interested in: they reflect how the mod.js and Python cores interact in Max6. I'm currently working on b994 revs of these core scripts, so anything strange happening with connection routines or entering/exiting/saving from the editor are very noteworthy, and extrememly helpful. It is because my implementation, by necessity, is so convoluted that I've delayed moving to Max6 for so long.
		+
		+	This particular problem is due to the wrong initalization order, and may be due some change in the behavior of [live.this_device]. I'm hoping to finish up with current Max5 stuff tonight and switch to Max6 for testing of a project tomorrow before release, so hopefully I'll be able to catch up with what's going on.

← Older revision		Revision as of 03:50, 1 July 2012
Line 28:		Line 28:
	#N: extra arguments for message "s"</nowiki>		#N: extra arguments for message "s"</nowiki>

		+
		+	Spent a total of about 3 hours trying to determine where that comes from over the last year....it drives me nuts.
		+
		+	It's an artifact from the original, I think, but I haven't been able to route it out. I think its harmless.

	===== general =====		===== general =====

@@ Line 1: / Line 1: @@
 It's possible that some of these '''aren't''' Max 6 related, but that's what I'm testing with, so...
-aumboids says "#N: extra arguments for message "funnel""
+Probably good to specify the test environment:
-presscafe: help goes to "Presscafe" rather than "PressCafe" (I've already made a redirect)