Hi,
while importing Max patches with cyclone I recently was again hit by the "counter" nameclash: I actually wanted cyclone's counter, but what I did get was the MarkEx counter, which I had totally forgotten about and of course, because of this Gem was the last library I disabled from .pdrc to find out where the wrong counter originated.
So I have a feature request: I would suggest to remove [counter] from the default Gem build.
It is not specific to Gem at all, not used in any help files, not compatible with the Max [counter] and there already are at least 4 other [counter] objects.
Ciao
Frank Barknecht wrote:
Hi,
while importing Max patches with cyclone I recently was again hit by the "counter" nameclash: I actually wanted cyclone's counter, but what I did get was the MarkEx counter, which I had totally forgotten about and of course, because of this Gem was the last library I disabled from .pdrc to find out where the wrong counter originated.
So I have a feature request: I would suggest to remove [counter] from the default Gem build.
right. i once asked whether it was ok for everybody if i removed MarkEx from Gem, but nobody but Hans replied.
so i guess everybody agrees...
It is not specific to Gem at all, not used in any help files, not compatible with the Max [counter] and there already are at least 4 other [counter] objects.
man, that's history!!
mfg.asdr IOhannes
Ciao
IOhannes m zmoelnig wrote:
right. i once asked whether it was ok for everybody if i removed MarkEx from Gem, but nobody but Hans replied.
and speaking of removing: any objection to get rid of [gemorb], [gemtablet] and other input devices, which could be handled better by [hid] or such.
i think [gemmouse] is fine, as it is bound to the window, but i have never tested [gemtablet] nor [gemorb]: for the former i guess that it emits absolute coordinates, so it is not (necessarily) bound to the gem-window, for the latter i don't know (but i guess it is the same)
so i guess everybody agrees...
mfg.asdr. IOhannes
Hallo, IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:
IOhannes m zmoelnig wrote:
right. i once asked whether it was ok for everybody if i removed MarkEx from Gem, but nobody but Hans replied.
and speaking of removing: any objection to get rid of [gemorb], [gemtablet] and other input devices, which could be handled better by [hid] or such.
i think [gemmouse] is fine, as it is bound to the window, but i have never tested [gemtablet] nor [gemorb]: for the former i guess that it emits absolute coordinates, so it is not (necessarily) bound to the gem-window, for the latter i don't know (but i guess it is the same)
I could never get [gemtablet] to work on Linux, so I wouldn't miss it. I use [gemmouse] a lot, also [gemkeyname], so please keep these. ;)
Ciao
Frank Barknecht wrote:
Hallo, IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:
IOhannes m zmoelnig wrote:
right. i once asked whether it was ok for everybody if i removed MarkEx from Gem, but nobody but Hans replied.
and speaking of removing: any objection to get rid of [gemorb], [gemtablet] and other input devices, which could be handled better by [hid] or such.
i think [gemmouse] is fine, as it is bound to the window, but i have never tested [gemtablet] nor [gemorb]: for the former i guess that it emits absolute coordinates, so it is not (necessarily) bound to the gem-window, for the latter i don't know (but i guess it is the same)
I could never get [gemtablet] to work on Linux, so I wouldn't miss it. I use [gemmouse] a lot, also [gemkeyname], so please keep these. ;)
i use them too.
i really just want to get rid of: [gemtablet] and even more of [gemorb]
mfg.adsr IOhannes
hi,
IOhannes m zmoelnig wrote:
right. i once asked whether it was ok for everybody if i removed MarkEx from Gem, but nobody but Hans replied.
its fine with me as long as the lib stays available.
and speaking of removing: any objection to get rid of [gemorb], [gemtablet] and other input devices, which could be handled better by [hid] or such.
never used them eather ... so for me its ok.
best
erich
FYI: a workaround for this is to use the namespace in Pd-extended:
[cyclone/counter]
That will ensure you always get the [counter] that you expect.
.hc
On Aug 12, 2006, at 4:03 AM, Frank Barknecht wrote:
Hi,
while importing Max patches with cyclone I recently was again hit by the "counter" nameclash: I actually wanted cyclone's counter, but what I did get was the MarkEx counter, which I had totally forgotten about and of course, because of this Gem was the last library I disabled from .pdrc to find out where the wrong counter originated.
So I have a feature request: I would suggest to remove [counter] from the default Gem build.
It is not specific to Gem at all, not used in any help files, not compatible with the Max [counter] and there already are at least 4 other [counter] objects.
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
------------------------------------------------------------------------
The arc of history bends towards justice. - Dr. Martin Luther King, Jr.
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
FYI: a workaround for this is to use the namespace in Pd-extended:
[cyclone/counter]
That will ensure you always get the [counter] that you expect.
I know about namespaces, but they won't help at all here: Problem is I'm importing Max patches, where people just use [counter], not [cyclone/counter] or [Gem/counter]. With the wrong [counter] active, there will be missing or wrong connections as a result.
After the import I'm removing all [counter]s anyway and replace them with attached [f0]x[+1] like it should be.
Ciao