Adam Murray

feature-request-jit-cellblock-in-place-edit-mode

> 2) Provide a way to cancel my edit. Sometimes I start typing and

> realize I am in the wrong cell, but it is already too late. I'd like

> to hit ESC and revert the cell contents to what they were when I

This is better done outside. just store a copy of the cell (or all 

cells) and if you hit esc write the old version back in. Shouldn't be 

too hard to patch... (you can refer the jit.cellblock to a coll, and 

then switch references to a second coll or something like that...)

Adam Murray schrieb:
> 2) Provide a way to cancel my edit. Sometimes I start typing and
> realize I am in the wrong cell, but it is already too late. I'd like
> to hit ESC and revert the cell contents to what they were when I
> first clicked on the cell.

This is better done outside. just store a copy of the cell (or all 
cells) and if you hit esc write the old version back in. Shouldn't be 
too hard to patch... (you can refer the jit.cellblock to a coll, and 
then switch references to a second coll or something like that...)

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


Quote: Stefan Tiedje wrote on Wed, 19 September 2007 01:55

----------------------------------------------------

> This is better done outside. just store a copy of the cell (or all 

> cells) and if you hit esc write the old version back in. Shouldn't be 

> too hard to patch... (you can refer the jit.cellblock to a coll, and 

> then switch references to a second coll or something like that...)

Well, I'm not sure it's "better" to do it outside. I disagree, but I bet we could argue all day about the pros and cons of keeping the core objects as simple as possible versus making them a bit more complicated for user friendliness.

Anyway your suggestion is a good idea so I gave it a shot, but I couldn't get it to work with in-place edit mode. It seems when a cell has focus, then no key presses register to the key object. Even if this did work, it only fixes my #2 issue. So I gave up on in-place edit mode and started using a textedit. This works better, but I ran into another issue. Check out the cellblock help file "editing_stuff" section and try clearing a cell's contents. When I hit delete & enter, it just redisplays the current cell contents. Does that seem like a bug to anyone else?

That's ok though, I worked around it as follows:

Now I'm wishing I could get focus back on the jit.cellblock after hitting enter or ESC in the textedit, so I could navigate the cellblock with the keyboard. But I started down this path because I wanted to use the mouse :/ Can't get the best of both worlds, I guess, but I am happy enough with the above patch.

Quote: Stefan Tiedje wrote on Wed, 19 September 2007 01:55
----------------------------------------------------
> This is better done outside. just store a copy of the cell (or all 
> cells) and if you hit esc write the old version back in. Shouldn't be 
> too hard to patch... (you can refer the jit.cellblock to a coll, and 
> then switch references to a second coll or something like that...)
>

Well, I'm not sure it's "better" to do it outside. I disagree, but I bet we could argue all day about the pros and cons of keeping the core objects as simple as possible versus making them a bit more complicated for user friendliness. 

Now I'm wishing I could get focus back on the jit.cellblock after hitting enter or ESC in the textedit, so I could navigate the cellblock with the keyboard. But I started down this path because I wanted to use the mouse :/  Can't get the best of both worlds, I guess, but I am happy enough with the above patch.

> It seems when a cell has focus, then no key presses register to the

> key object. Even if this did work, it only fixes my #2 issue.

Yes, that's a problem. The workaround with that could be the hi object 

if you're on a Mac. It will give you output even if the focus is on an 

> That's ok though, I worked around it as follows:

Adam Murray schrieb:
> It seems when a cell has focus, then no key presses register to the
> key object. Even if this did work, it only fixes my #2 issue.

Yes, that's a problem. The workaround with that could be the hi object 
if you're on a Mac. It will give you output even if the focus is on an 
object...

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

cycle~ has a default table. You can change it if you want. See the

> Why, in cycle~ we have a "cosines" table instead a sinus one ?

> It is something related with synchronization (in cosine the "1" is

> always the begin of the period, and in the sinus wave the "0" appears

cycle~ has a default table.  You can change it if you want.  See the
msp docs for further info.
wes

On 10/1/07, Mikhail Malt  wrote:
> Hi all
>
>
> Why, in cycle~ we have a "cosines" table instead a sinus one ?
> It is something related with synchronization (in cosine the "1" is
> always the begin of the period, and in the sinus wave the "0" appears
> twice in a cycle)?
>
>   thanks in advace
>
> Mikhail
>
>
>
>
>


> cycle~ has a default table. You can change it if you want. See the

This I know, the question is "why a cosines instead a sine wave table"???

In the doc we can't find the "why is a cosine". In fact it is said thatis

a sine table.. what seems that is wrong..(try freq = 0, and changing the

> cycle~ has a default table.  You can change it if you want.  See the
> msp docs for further info.
> wes
>
This I know, the question is "why a cosines instead a sine wave table"???
In the doc we can't find the "why is a cosine". In fact it is said thatis
a sine table.. what seems that is wrong..(try freq = 0, and changing the
phase..)

Feature Request: jit.cellblock in-place edit mode