Processing 123 makes programming impossibly difficult on French Mac keyboards, as we can
no longer type square brackets: [ ]. On a French keyboard, round brackets are on the same
key as the 5 key. To get square brackets, you have to press:

alt + shift + (

and as I mentioned the "(" sign is on the same key as "5".

I don't know if all this is clear. But anyway, when trying to type a square bracket Processing
123 instead moves to the next/previous tab. This appears to be by design, and not a bug, in
fact.

We have moved back to 121 to avoid this problem. No problems there.

yikes! that's no good, let's fix this before 0124.

though i don't understand what's going on... cmd-{ and cmd-} should move
forward/backward a tab, not alt-{ and alt-} is that not what's happening on
your keyboard? does alt-?? get used for all menu commands on the french
keyboard?

I'm downloading 123 on this computer to find out if ALT has become the new CMD.
Everyone in the lab has been using 121, and I've also gotten a lot of email from strangers
who use my online classes to learn Processing (apparently I'm the french help desk, which is
too bad because they should really be contributing their questions to the main site).

Uh, strange, on this computer at home I get "{" fine, but NO TABS! WTF? Not even from
the menu. This is becoming all confusing. I'll get back to you on this when I get to the lab
on Thursday. It might be some sort of Mac-thing.

(In reply to comment #1)
>
>
>
> Additional Comment #1 From
>
> fry
> 2007-01-29 19:21
>
> <!--
> addReplyLink(1); //-->[reply]
>
>
>
>
> yikes! that's no good, let's fix this before 0124.
>
> though i don't understand what's going on... cmd-{ and cmd-} should move
> forward/backward a tab, not alt-{ and alt-} is that not what's happening on
> your keyboard? does alt-?? get used for all menu commands on the french
> keyboard?

that's very strange, but i do know the text editor has some quirks. please
let me know what you find out, i'd very much like to fix it asap.

ah, found and fixed for 0125. we'll also be switching to a character that's
not a bracket anyway, but i managed to track down the issue. thanks for the
report.