how to disable loadbang (and/or, window flags float bug)
I have a peculiar problem, I probably found a bug or perhaps I don’t know about some features.
I have a window with thispatcher in it that, via loadbang makes it a floating window and bangs window exec. I have not provided myself a way out and now I can’t even edit anything inside this patcher. This, I guess, is a bug (I can enter edit mode but cannot delete or create any objects). This is on windows, if it at all matters.
So, right now, I am thinking that there must be a way to tell max not to activate loadbang when loading a patch (or perhaps this is my pure data overdose).
I tried to open the patch in a text editor, but .pat is a binary file. Copying the contents to paste elsewhere does not work either (it pastes/instantaites a new abstraction). So I am effectively locked out of a patcher.
I’m out of ides. Anyone?
> I have a window with thispatcher in it that, via loadbang makes it a
> floating window and bangs window exec. I have not provided myself a
> way out and now I can’t even edit anything inside this patcher.
> This, I guess, is a bug (I can enter edit mode but cannot delete or
> create any objects). This is on windows, if it at all matters.
On a Mac you would hold shift-cmd while loading the patch to disable
lodbangs. I guess on Windows its shift-ctrl. It does not work with
loadmess or patcherargs…
The other way to do it is to open the patch as text, search for the
"window exec" and just remove the exec (don’t remove the whole line,
just the word exec…). Then it should open fine again…
And make a backup of the patch before you start messing with the text
Quote: Stefan Tiedje wrote on Wed, 08 August 2007 23:53
> …Then it should open fine again…
although, I’ve done this before only to find all my patch cords have moved.
robin foster schrieb:
> Quote: Stefan Tiedje wrote on Wed, 08 August 2007 23:53
>> …Then it should open fine again…
> although, I’ve done this before only to find all my patch cords have moved.
> be prepared…
You must not delete a whole line, just rename the offending object to
somthing max won’t find, then it will be replaced with a bogus object
retaining all connections but not doing anything…
save as text, open, use find and replace to change "loadbang" to "stfu" or whatever you feel like… then open. also make a backup of the original.
cool. knowing that could have saved me a huge amount of trouble in the past
I had the same problem when experimenting with floating windows. I think it has to do with the key focus not being able to be set to the window, as it’s "part of" the underlying window or something. Yeah, I couldn’t do any deletions etc., it was pretty strange. However, all the mouse commands still work, so you can right-click and choose Clear to delete, or use copy, paste, etc. So just copy a message box with "nofloat etc." and paste it in.
The text fix will certainly work, and that’s a good lesson in general: no Max patch will do *anything* until you click something or provide a loadbang / loadmess. I had a worse problem once whereby a loadbang generated a stack overflow and crashed Max immediately. I just erased the loadbang in the text and that was that, but it was pretty rough until I figured that out… I thought my patch was dead and gone. (or more accurately, poisonous ;-)
Along the lines above, perhaps an Get Info / Inspector for subpatches would be cool: manage window state, size and placement, other (?) — — Maybe this isn’t possible the way Inspectors work, but it’s just a thought… would eliminate the need for the window-state scripting and positioning / resaving, though I guess it’s really not that much of a hassle anyways.
Forums > MaxMSP