It’s the first time i’m in this situation.
I usualy developpe patches for musicians, composers or… myself :-)
Anyway, this time, the patch i developped is for a company so the way the UI looks is (i’m sorry musicians and composers) more important.
I means, not only it has to work well (that’s the least i can do) but it also has to look really nice.
For the first time in my maxer life, i’m planning to use the fpic object.
The problem with this object is that, in the inspector window, you have to give the path to the picture you want to use.
I don’t want to give this company a collective or a standalone as i want them to be able to edit the patch if they need to… (something like an Open Source software :-) )
So if i use the fpic object, the path will be different on tehir computer. So when they’ll open the patch, they will get max error messages saying that Max cannot find the pic.
Do you know any trick i could use so that fpic (or something else) would search for the pic it has to load in the current folder (where the patch itself is located) and not in the path entered in the inspector window ?
I hope i’m clear.
Thanks for your wise suggestions :-)
I don’t want to give this company a collective or a standalone as i
want them to be able to edit the patch if they need to… (something
like an Open Source software :-) )
I’m not a tech support guy, but this sounds iffy. If you really want
to make this open source software, compile a stand alone and put the
source into a "src011xp|| folder" so they DONT SCREW IT UP!
again, I’m no tech support guy, but you also dont want to end up
basically paths for pictures an not different
than pths to subpatchers – when they are in the
search path of the runtime, the will be found again.
so the only thing you have to be careful about is
naming; always make sure you use unique names for
your projects so that you can keep everything inside
the search path. ("knob.pct" is a bad idea!)
On Oct 21, 2006, at 2:59 AM, tworowski.sebastien wrote:
> Do you know any trick i could use so that fpic (or something else)
> would search for the pic it has to load in the current folder
> (where the patch itself is located) and not in the path entered in
> the inspector window ?
If it’s a static background you could just copy the pic in your image
editing app, paste it into the patch, then make the picture a part of
the background. You could include the original picture in a source
elements directory if the client will need to edit it in the future.
The client could also just copy the image back out of the patcher and
paste it into their own editing app.
This is how I like to do it… no paths or image loading needed. I
often do basic layout of gui elements in Max, then snap a screenshot
and refine the interface in Photoshop, then lay the background back
in the patcher and create custom controls to fit.
Urbi et orbi