While I'm at it: Minor Frustration, the 3rd:

Max is very "helpful" when I'm writing. For example, I'd like my coming super-app to flash "version 1.0", but Max insists there's no need for a zero after the dot. I insist there is, but Max has his own will...

Worse: any decent mac application (like those I'm building) should have their Preferences available by the shortcut ?, (apple-comma). Well, try typing /, in the menubar object at the end of a line, activate the menubar (works fine), save+close the patch, open again, activate menubar - doesn't work (backslash and comma gone).

Sometimes I *do* know what I want, even though Max thinks he knows better. Can anyone help me get my will?

me-writing-max-correcting

Thanks a lot again. Making the text as one string with quotes works, I should have thought about that. Menubar in a patcher edited as text and saved as text also works, with no extra backslashes. More backslashes doesn't work. I'll have to have the menubar as an abstraction then.

Yeah I know, I'm very concerned about my looks! Certainly more so than Max is. Especially when making things that other people will use, the user experience is important.

Ultimately, I'd like to have a lot more control over the menu bar than the menubar object offers. For example, the mac convention says that Preferences should be located in the Application menu, beneath the "about..." item, and I'd like to be able to put it there. And my apps have some window management options which really belong to the Window menu, but I have no access to that menu.

Some other purely cosmethic items on my wishlist: (Better) anti-aliasing for text and stock graphics, and real alpha channel support for pics (grayscale, allowing opacity gradients). Alignment choices for number boxes, and OS-specific menu styles. But I know I may be among the very few maxers concerned about such things. Then again, I should probably get over it and learn Java, that might help a little.

Ultimately, I'd like to have a lot more control over the menu bar than the menubar object offers. For example, the mac convention says that Preferences should  be located in the Application menu, beneath the "about..." item, and I'd like to be able to put it there. And my apps have some window management options which really belong to the Window menu, but I have no access to that menu.

Some other purely cosmethic items on my wishlist: (Better) anti-aliasing for text and stock graphics, and real alpha channel support for pics (grayscale, allowing opacity gradients). Alignment choices for number boxes, and OS-specific menu styles. But I know I may be among the very few maxers concerned about such things. Then again, I should probably get over it and learn Java, that might help a little.


Quote: dhk wrote on Tue, 01 August 2006 10:35

----------------------------------------------------

> Some other purely cosmethic items on my wishlist: (Better) anti-aliasing for text and stock graphics, and real alpha channel support for pics (grayscale, allowing opacity gradients). Alignment choices for number boxes, and OS-specific menu styles. But I know I may be among the very few maxers concerned about such things. Then again, I should probably get over it and learn Java, that might help a little.

i'm pretty sure that alpha channel support for pics, will be one of the improvements in max version 5.0...i read it in a prevoius thread ;)

Quote: dhk wrote on Tue, 01 August 2006 10:35
----------------------------------------------------
> Some other purely cosmethic items on my wishlist: (Better) anti-aliasing for text and stock graphics, and real alpha channel support for pics (grayscale, allowing opacity gradients). Alignment choices for number boxes, and OS-specific menu styles. But I know I may be among the very few maxers concerned about such things. Then again, I should probably get over it and learn Java, that might help a little.
----------------------------------------------------

i'm pretty sure that alpha channel support for pics, will be one of the improvements in max version 5.0...i read it in a prevoius thread ;)


The rs.objects seem very attractive, the numbox also solving the "Round Problem" I complained about in another thread (well, two threads, actually - accidental double post, the other now named "-" and meant to die, but answered while I was editing it - max forum folks can be extremely quick!). A couple of things holding me off them, though: the compatibility issue makes me want to stick to stock objects as far as I can (UB, Windows, having to make sure all my partners have all the appropriate externals, and OS version to run them). And the License Agreement with it's VERY LOUD UPPERCASE STATEMENTS scares me. If I sometime in the future slip and create something commercial with an rs. bit, I fear Roby might send some very dangerous guys knocking on my door...

Me writing, Max "correcting"