Hi Thomas,
Am Montag, den 06. Mai 2002 um 01:27:18 Uhr (+0200) schrieb Thomas Musil:
very nice improvement of gate. but I would change the "max_10_outlet-restriction".
I should have thought about it right away. Thanks for the addition... Another question remains: How can the outlets be accessed in the gui? If there are more than 6 outlets even now the outlet connectors get blurred as the width of the object is too small.
Is there a way to stretch the object horizontally?
I didnt have any time to test the pd-max compatibility lib. maybe there will be a conflict with gate-object? in next-max of the early 90's, the left input was the contol-input, the same in max-msp (i think). so i will test the max-compatibility lib and decide to rename gate-object. the change is in the attachment.
You are right: The inlets are still the other way around in Max. I left it that way mainly for backwards compatibility reasons in pd and because it makes more sense if the control input is the right one. How shall I go about it? It could be changed using a proxy and we could use two different names. For Max compatibility it would be nice if the name for the pd-style object would change (and also the handling of creation arguments), but that would break backwards compatibility in pd.
Yours, Orm
P.S.: BTW: What about a Max compatible "switch" object? Does something like that already exist in pd? I need something like that all the time.
hi Orm, hi Thomas...
Orm Finnendahl wrote: ...
Am Montag, den 06. Mai 2002 um 01:27:18 Uhr (+0200) schrieb Thomas Musil:
...
I didnt have any time to test the pd-max compatibility lib. maybe there will be a conflict with gate-object?
what library have you in mind? There is no gate in pd-lib, nor
in cyclone (yet). But... there is an xgate' external coded by CK aka chris at lo-res.org (which, btw, limits the number of outlets to 10). And... there is ademux' in zexy.
...
in next-max of the early 90's, the left input was the contol-input, the same in max-msp (i think).
gate in max has a bang method too (reports the open outlet), which is probably the only reason why the inlets are as they are. One needs to filter this bang through a [grab], though (there is a grab class in cyclone).
...
P.S.: BTW: What about a Max compatible "switch" object? Does something like that already exist in pd? I need something like that all the time.
ok, if nobody has it up an running, I think I will give it a try (when I am through the huge pile of mail:-)
Krzysztof
Hi all,
I often have the same problem with objects that have a lot of inlets / outlets. I know there is a way to stretch an object by writing a lot of code for the object itselfe....
Wouldn't it be a good idea to change the Pd code slightly so that object sizes do not only depent on the length of the object's name? I haven't had a look at the code yet but my idea is to check wether the inlets / outlets overlap. I.e. when Pd calulates the horizontal size for an object (based on the number of characters I think ?) it checks wether it will be long enough for all inlets / outlets (leaving at least one pixel between them) and makes it longer if necessarry....
My workaround was to use somtheing like this: [object any_text_to_stretch_it] - But this makes a patch look like a text book... and might suggest that a creation argument is passed on to the object.
Olaf
Orm Finnendahl wrote:
If there are more than 6 outlets even now the outlet connectors get blurred as the width of the object is too small.
Is there a way to stretch the object horizontally?
Am Dienstag, den 07. Mai 2002 um 12:12:00 Uhr (+0200) schrieb Olaf Matthes:
My workaround was to use somtheing like this: [object any_text_to_stretch_it] -
That's what I came up with after my post, too. I use a Sequence of underscores as an additional argument. This looks nice. The only problem could arise, when you don't want to initialize an object with arguments but still want to stretch it. And it wastes space if you store the object. It'd be nice, if a (optional) horizontal stretch factor could be saved with the patcher (as integer number on a grid of characterwidth pixel values).
-- Orm
-
Krzysztof Czaja -
Olaf Matthes -
Orm Finnendahl