Another Prepend bug report

Feb 6, 2007 at 4:32am

Another Prepend bug report

Max 4.6.2

Jitter 1.6.2 (n/a ?)

OS X 10.4.8

Macbook Pro 2.33Ghz 3Gb Ram

Issue:

Inconsistent escape character handling and display with Prepend object

Bug:

open attached patch

Prepend was instantiated as [prepend set "] as it (set ” being its
arguments).

Upon closing and re-opening the patch, the escaping is no longer
displayed.

User can enter simply ‘ or ” AFTER the initial “

(ie [prepend set " " " "] (note that the first escape char is no
longer displayed, however the first ” was entered as “)

Now, delete the first double quote and its preceding whitespace (the
one that initially had the “)

None of the following double quotes are prepended anymore.

Odd? Took me a while to figure this one out. Seems like something odd
is going on?

I DO have to escape ” right? If I instantiate a new prepend object
sans escape char, I dont get any prepended double quotes.

v a d e //

http://www.vade.info
abstrakt.vade.info

#30135
Feb 6, 2007 at 6:21am

I’ve seen similar issues with escape characters before. I can’t open
your patch. Can you paste it as text or zip it? Max patches tend to
get corrupted when attached bare.

wes

#95687
Feb 6, 2007 at 6:47am

Here you go:


Thanks for checking it out Wes :)

On Feb 6, 2007, at 1:21 AM, Wesley Smith wrote:

> I’ve seen similar issues with escape characters before. I can’t open
> your patch. Can you paste it as text or zip it? Max patches tend to
> get corrupted when attached bare.
>
> wes

v a d e //

http://www.vade.info
abstrakt.vade.info

#95688
Feb 6, 2007 at 7:03am

If I take [prepend set "] and cmd+d it the ” disappears. I’ve had
problems escaping commas in message boxes disappear after closing and
reopenning before. I guess this could be considered a bug but I’m no
expert on escape sequences in Max’s current text environment. I bet
Peter Castine knows. Anyway, what is the final result you’re looking
for?

wes

#95689
Feb 6, 2007 at 7:17am

Consistency.

Its just awkward, especially considering entering other, non escaped
double quotes will work even after the first escape has vanished but
is still in effect, until you delete its whitespace, then the other
used to be working, non escaped double quotes STOP working. Its just
weird, inconsistent and doesnt build trust.

Did you take a look at the other imageunit + prepend crasher I
pointed out before?

This isnt so huge, but I was just poking around with prepend to see
if I could find anything odd with it, due to the crashing from above.

I just get a little nervous when I see text ive entered.. vanish.

Thats not so good afaik.

Thanks :)

On Feb 6, 2007, at 2:03 AM, Wesley Smith wrote:

> If I take [prepend set "] and cmd+d it the ” disappears. I’ve had
> problems escaping commas in message boxes disappear after closing and
> reopenning before. I guess this could be considered a bug but I’m no
> expert on escape sequences in Max’s current text environment. I bet
> Peter Castine knows. Anyway, what is the final result you’re looking
> for?
>
> wes

v a d e //

http://www.vade.info
abstrakt.vade.info

#95690
Feb 6, 2007 at 7:18am

BTW< I havent been able to repeat it, but ive also occasionally
gotten non escape characters to delete as well ( I loose the whole
“, not just ), but I cant get it to repeat, so I havent reported it
as a bug. Just fyi.

Thanks.
On Feb 6, 2007, at 2:03 AM, Wesley Smith wrote:

> If I take [prepend set "] and cmd+d it the ” disappears. I’ve had
> problems escaping commas in message boxes disappear after closing and
> reopenning before. I guess this could be considered a bug but I’m no
> expert on escape sequences in Max’s current text environment. I bet
> Peter Castine knows. Anyway, what is the final result you’re looking
> for?
>
> wes

v a d e //

http://www.vade.info
abstrakt.vade.info

#95691
Feb 6, 2007 at 8:35am

On 6-Feb-2007, at 8:03, Wesley Smith wrote:
> If I take [prepend set "] and cmd+d it the ” disappears. I’ve had
> problems escaping commas in message boxes disappear after closing and
> reopenning before. I guess this could be considered a bug but I’m no
> expert on escape sequences in Max’s current text environment. I bet
> Peter Castine knows.

I can only attempt to deduce from what I have observed. Those with
access to the source code might be able to deliver a more
authoritative analysis.

What I have observed: every time text goes through the Max parser
(which analyses raw text and turns it into a sequence of ints,
floats, symbols, commas, dollars and ‘semis’), when it comes across
the byte-sequence backslash-anything, the backslash is swallowed and
the ‘anything’ is taken as a literal rather than a character with
special meaning. When rendering a sequence of ints, symbols, etc.,
Max just renders the text as is.

This is not a problem until you need to edit the text, at which point
it gets parsed again, and if you haven’t manually re-entered any
necessary backslashes, you’re hosed.

Is this a bug or a feature?

The behavior is not documented anywhere I am aware of, and when
people actually notice it, it seems pretty inconvenient.

However, if DDZ changes the behavior, I wouldn’t be surprised if a
bunch of people come screaming about how they rely on the old system.

Sorry, Wes, I’m not sure I’m winning any wagers for you today.
Lawdie, it’s tough having a rep to live up to.-)

————– http://www.bek.no/~pcastine/Litter/ ————-
Peter Castine +–> Litter Power & Litter Bundle for Jitter
Universal Binaries on the way
iCE: Sequencing, Recording &
Interface Building for |home | chez nous|
Max/MSP Extremely cool |bei uns | i nostri|
http://www.dspaudio.com/ http://www.castine.de

#95692
Feb 6, 2007 at 4:16pm

vade wrote:
> open attached patch

It doesn’t open, pasted text never fails…

How often do I have to bang this dead horse? Even if it would open its a
very bad idea to attach a patch instead of pasting. If you want others
to look at it you should make it simple…

Stefan (sorry)


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com

#95693

You must be logged in to reply to this topic.