Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (athena.apache.org: domain of webdoublefx@hotmail.com
 designates 157.55.2.100 as permitted sender)
Message-ID: <DUB402-EAS224C5AC7796C1C7F20FB0C0B4310@phx.gbl>
From: =?iso-8859-1?Q?Fr=E9d=E9ric_THOMAS?= <webdoublefx@hotmail.com>
To: <dev@flex.apache.org>
References: <CE4AAC97.11800%aharui@adobe.com>
 <3E2B6E5D-5D96-484A-847E-10CF8965CB37@gmail.com>
In-Reply-To: <3E2B6E5D-5D96-484A-847E-10CF8965CB37@gmail.com>
Subject: RE: Shift Enter in TLF
Date: Tue, 3 Sep 2013 14:12:31 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thread-Index: 
 AQABAgMEqZ7UvIaY+mczqf1WqelhmwCKQxRBABg8I14AQXLFlQALhuUNAE6buEMAfLNw/wAlyUwyALFIpBsAgW9HfAAxzJrdnTUQ4NA=
Content-Language: fr

Windows users should redo with CTRL+Y

-----Message d'origine-----
De=A0: Harbs [mailto:harbs.lists@gmail.com]=20
Envoy=E9=A0: mardi 3 septembre 2013 14:11
=C0=A0: dev@flex.apache.org
Objet=A0: Re: Shift Enter in TLF

Okay. I pushed my changes out.

I added a flag in Configuration with three levels. Default is always =
soft
returns, but it could be changed by the user both at the class level =
(using
tlf_internal) and in the individual configuration object. I don't know =
if
the user needs that level of control, but it was not a big deal to offer =
it,
so I figured why not...

I also added Command+Shift Z for redo. It seems to work on Mac and do
nothing on Windows (which I think is the proper behavior there).

On Sep 3, 2013, at 7:00 AM, Alex Harui wrote:

>=20
>=20
> On 9/2/13 1:03 PM, "Harbs" <harbs.lists@gmail.com> wrote:
>=20
>> I've done both the shift return and command+shift z for redo. I've=20
>> tested on Mac. I'll try to test on Windows before I commit.
>>=20
>> Question: How should shift-return behave within lists? Should they=20
>> behave like regular paragraphs where it only inserts a soft return,=20
>> or should it create a hard return without creating a new list item?
>>=20
>> I'm coming from InDesign where a new paragraph is always a new list =
item.
>> Unless you break the list completely, you need a soft return to break =

>> a list item. I'd like to mimic the InDesign paradigm. Any objections? =

>> Does it need an option to change the behavior? If yes, would=20
>> IConfiguration be a good place to set that?
> I don't know enough to have an opinion.  If you are making significant =

> changes to existing behavior, a flag would be nice, but not required.
>=20
> -Alex
>=20