Pitfalls for Maxers - Revision history

Diemo: rm old bug

2011-04-27T13:34:59Z

rm old bug

Diemo at 12:22, 23 June 2008

2008-06-23T12:22:13Z

Diemo: from freesoftware/wiki

2008-06-23T12:21:42Z

from freesoftware/wiki

Diemo: idx, obj

2008-06-23T12:01:48Z

idx, obj

New page

* Indexing of [[FTM]] matrices is in ''row, column'' order, as is usual in mathematics. Max uses ''column, row'' like coordinates in pixel graphics.

* There are a number of [[Max objects having problems with FTM data objects | Max objects that sometimes don't respond well to atoms containing FTM data objects]].

← Older revision		Revision as of 13:34, 27 April 2011
Line 11:		Line 11:

	* '''Indexing''' of [[FTM]] matrices is in ''row, column'' order, as is usual in mathematics. Max uses ''column, row'' like coordinates in pixel graphics.		* '''Indexing''' of [[FTM]] matrices is in ''row, column'' order, as is usual in mathematics. Max uses ''column, row'' like coordinates in pixel graphics.
−
−	* '''Don't click''' inside of the [[FTM message box]] when trailing a patch cord with your mouse after accidentally typing a character. (FTM will crash because we're not able to detect this because the Max API doesn't allow us to catch this event.)

	[[Category:FAQ]]		[[Category:FAQ]]

← Older revision		Revision as of 12:22, 23 June 2008
Line 13:		Line 13:

	* '''Don't click''' inside of the [[FTM message box]] when trailing a patch cord with your mouse after accidentally typing a character. (FTM will crash because we're not able to detect this because the Max API doesn't allow us to catch this event.)		* '''Don't click''' inside of the [[FTM message box]] when trailing a patch cord with your mouse after accidentally typing a character. (FTM will crash because we're not able to detect this because the Max API doesn't allow us to catch this event.)
		+
		+	[[Category:FAQ]]

← Older revision		Revision as of 12:21, 23 June 2008
Line 1:		Line 1:
−	* Indexing of [[FTM]~~] matrices is in ''row, column'' order, as is usual in mathematics~~. ~~Max uses ''column, row'' like coordinates in pixel graphics~~.	+	This page tries to list the most common errors die hard Maxers fall into when getting started with [FTM].
		+	Please add your own experience...

−	* There are a number of [[Max objects having problems with FTM data objects \| Max objects that sometimes don't respond well to atoms containing FTM data objects]].	+	* '''Don't use''' Max's <tt>print</tt> to display [[FTM objects]], '''Use''' <tt>ftm.print</tt>.
		+
		+	* There are a number of other [[Max objects having problems with FTM data objects \| Max objects that sometimes don't respond well to atoms containing FTM data objects]].
		+
		+	* '''Don't use''' Max's <tt>loadbang</tt> to trigger FTM stuff (that uses FTM references). Some references may not be fully initialised yet. '''Use''' an [FTM message box] with the ''loadbang'' option enabled in its inspector.
		+
		+	* '''Don't forget''' that [FTM objects] are sent around as '''references''', i.e. when you change the data, the original object is changed. Use <tt>trigger l l l</tt>, and <tt>ftm.copy</tt> when necessary.
		+
		+	* '''Indexing''' of [[FTM]] matrices is in ''row, column'' order, as is usual in mathematics. Max uses ''column, row'' like coordinates in pixel graphics.
		+
		+	* '''Don't click''' inside of the [[FTM message box]] when trailing a patch cord with your mouse after accidentally typing a character. (FTM will crash because we're not able to detect this because the Max API doesn't allow us to catch this event.)