Zoom or Scale content of bpatcher
Hi,
Is there a supported means to display a zoomed or scaled view of a bpatcher?
My needs are fairly simple... and, don't need dynamic zoom. If I could have 3 predefined scale factors on buttons, that would suffice.
I see some old dialogs about unsupported zoomfactor, but not sure that's the best route to take.
Any guidance would be much appreciated!
Peace~
Zoomfactor works like the offset message. You need to send it to a thispatcher inside of the bpatcher. Here's a quick example:
Your example helped a lot. BIG Thanks!
Might you offer a little more guidance? Spent almost a week trying to figure this out on my own...
When I send 0.7 to zoomfactor to thispatcher, the bpatcher is scaled down - GREAT!
But, it's also offset the X by 140 pixels.
If I then send 1.0 to restore to the original position, the scaling looks correct, but the X offset is now -20 pixels.
If I repeat this (eg, zoom out zoom in) the X offset gradually moves more and more to the left, each time the 1.0 pushing another -20 pixels.
1st - trying to figure out/find a comment to set the X offset for the bpatcher when sending 0.70
2nd - figuring out why the display keeps jogging to the left
I'm not very skilled with Max and appreciate any further guidance.
Thank you!
Update -
When sending the 1.0 to zoomfactor, previously noted that the X offset is then -20 pixels. Additionally the Y offset is now -140 pixels
While repeated 1.0 0.7 1.0 0.7 events continue to move the display further to the left, the Y offset for the 1.0 remains at -140 pixels.
Can't believe how simple this was... or how long it took to find the solution after so many hours of pouring over the documentation... mostly guessing at this and that...
sending the following message to thispacher solved the problem...
offset -200 0
Thanks again for your help MZED~!!!
This ZOOMFACTOR is super - I couldn't find even a word about it in "thispatcher" or "bpatcher" documentation/reference/help - is it possible, that I was looking wrong, or some features/attributes/messages of objects sometimes are missing in documentation? I wish I was looking wrong, of course..
I think you're correct, some features seem to be undocumented-- they were perhaps only intended to be used by the developers of the software and not the retail consumers