From ftm
(from freesoftware/wiki) |
|||
| 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]] | ||
Revision as of 13:22, 23 June 2008
This page tries to list the most common errors die hard Maxers fall into when getting started with [FTM]. Please add your own experience...
- Don't use Max's print to display FTM objects, Use ftm.print.
- There are a number of other Max objects that sometimes don't respond well to atoms containing FTM data objects.
- Don't use Max's loadbang 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 trigger l l l, and ftm.copy 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.)