jake rodriguez

I know it is 'unsupported', but the 'opened' object that is quite useful to us standalone freaks is not working in the 4.6.1 runtime environment when working on an intel machine. If you build the standalone below on 4.6.1 and run on a powerpc machine, when you drop a text file on the app icon it will open to report the pathname to the status window (provided, for some reason, you remove the cfm extension package from the resources folder). On an Intel machine, this does not occur as expected. Posted here for the hope of a quiet fix at some point and also for notification of other users of this useful 'unsupported' object. Does anyone know of another means to grab apple open events data that would be UB compatible?

I know it is 'unsupported', but the 'opened' object that is quite useful to us standalone freaks is not working in the 4.6.1 runtime environment when working on an intel machine.  If you build the standalone below on 4.6.1 and run on a powerpc machine, when you drop a text file on the app icon it will open to report the pathname to the status window (provided, for some reason, you remove the cfm extension package from the resources folder).  On an Intel machine, this does not occur as expected.  Posted here for the hope of a quiet fix at some point and also for notification of other users of this useful 'unsupported' object.  Does anyone know of another means to grab apple open events data that would be UB compatible?

unsupported-opened-object-doesnt-work-on-intel4-6-1

Fix will be in next updated version of MaxMSP

(unsupported) 'opened' object doesn't work on Intel/4.6.1