Numbered list item picks up from preceding nested list item
Hi Stacie,
This can be done in a number of ways.
I find it best with nested lists to start by deciding how deep you
will go. Let's say for three levels, set in the first level:
If level is: 1
If context is: {first}
Numbering properties
Autonumber format: L:< =0>< =0>\t *** hereby setting the
first counter to 1 and the 2nd and 3rd counter to 0***
Else
Numbering properties
Autonumber format: L:< >< >\t ***keeping the counters as empty***
If level is: 2
Autonumber format: L:.< >\t ***no need to account for first
here as the counter was already set in the first level.***
If level is: 3
Autonumber format:L:..\t
The level 2 and three can of course also be set with preceding counters empty.
Actually my numbering systems usually are a bit more complicated than
this plus I often use a kind of heading for the lists, so I can
connect it to the list by "Keep with next". This calls for a
duplication of setting the 1st level counter to 1 (or optionally first
level counter to 1 and following levels counters to 0).
I have an 18 month old part sample that looks like this:
Count ancestors named: List
If level is: 1
If context is: {after ListHead}
Numbering properties
Autonumber format: L:.\t
Else, if context is: {first}
Numbering properties
Autonumber format: L:.\t
Else
Numbering properties
Autonumber format: L:.\t
Else, if level is: 2
If context is: {after ListHead}
Numbering properties
Autonumber format: L:..\t
Else, if context is: {first}
Numbering properties
Autonumber format: L:..\t
Else
Numbering properties
Autonumber format: L:..\t
Else, if level is: 3
If context is: {after ListHead}
Numbering properties
Autonumber format: L:...\t
Else, if context is: {first}
Numbering properties
Autonumber format: L:...\t
Else
Numbering properties
Autonumber format: L:...\t
Else
Numbering properties
Autonumber format: NO NUMBERING BEYOND LEVEL 3
I could have saved some typing and set the 2nd and 3rd counters --
like in the first example -- at first level, thus eliminating the need
for the {first} context in 2nd and 3rd levels.
The last Else is a warning only.
Have fun!
Bodvar
On 11/22/05, Stacie Knas wrote:
> This is great! I never noticed that "Empty Counter" entry before. I
> followed your procedure, Lester, and it's perfecto! Thank you so
> much. What a great list. Thank you all.
> --Stacie
>
Re: Numbered list item picks up from preceding nested list item
Hi Stacie,
This can be done in a number of ways.
I find it best with nested lists to start by deciding how deep you
will go. Let's say for three levels, set in the first level:
If level is: 1
If context is: {first}
Numbering properties
Autonumber format: L:< =0>< =0>\t *** hereby setting the
first counter to 1 and the 2nd and 3rd counter to 0***
Else
Numbering properties
Autonumber format: L:< >< >\t ***keeping the counters as empty***
If level is: 2
Autonumber format: L:.< >\t ***no need to account for first
here as the counter was already set in the first level.***
If level is: 3
Autonumber format:L:..\t
The level 2 and three can of course also be set with preceding counters empty.
Actually my numbering systems usually are a bit more complicated than
this plus I often use a kind of heading for the lists, so I can
connect it to the list by "Keep with next". This calls for a
duplication of setting the 1st level counter to 1 (or optionally first
level counter to 1 and following levels counters to 0).
I have an 18 month old part sample that looks like this:
Count ancestors named: List
If level is: 1
If context is: {after ListHead}
Numbering properties
Autonumber format: L:.\t
Else, if context is: {first}
Numbering properties
Autonumber format: L:.\t
Else
Numbering properties
Autonumber format: L:.\t
Else, if level is: 2
If context is: {after ListHead}
Numbering properties
Autonumber format: L:..\t
Else, if context is: {first}
Numbering properties
Autonumber format: L:..\t
Else
Numbering properties
Autonumber format: L:..\t
Else, if level is: 3
If context is: {after ListHead}
Numbering properties
Autonumber format: L:...\t
Else, if context is: {first}
Numbering properties
Autonumber format: L:...\t
Else
Numbering properties
Autonumber format: L:...\t
Else
Numbering properties
Autonumber format: NO NUMBERING BEYOND LEVEL 3
I could have saved some typing and set the 2nd and 3rd counters --
like in the first example -- at first level, thus eliminating the need
for the {first} context in 2nd and 3rd levels.
The last Else is a warning only.
Have fun!
Bodvar
On 11/22/05, Stacie Knas <[EMAIL PROTECTED]> wrote:
> This is great! I never noticed that "Empty Counter" entry before. I
> followed your procedure, Lester, and it's perfecto! Thank you so
> much. What a great list. Thank you all.
> --Stacie
>
___
You are currently subscribed to Framers as [EMAIL PROTECTED]
To unsubscribe send a blank email to
[EMAIL PROTECTED]
or visit
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com
Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.
Numbered list item picks up from preceding nested list item
This is great! I never noticed that "Empty Counter" entry before. I
followed your procedure, Lester, and it's perfecto! Thank you so
much. What a great list. Thank you all.
--Stacie
On 11/22/05, Lester C. Smalley wrote:
> You can include the number or letter followed by a colon, you simply
> type the desired text into the EDD as content of the "Autonumber Format"
> element.
>
> However, I believe that you really want instead of designating these
> items as different numbering series (which is what the A: or N: do) you
> should include an EmptyCounter building block (will display as < > )
> before your existing counter. One empty counter should be used for each
> level of nesting, so a second-level list (first nested list) has one, a
> third level list has two, etc.
>
> For example:
>
> If level is 1:
>...
> If context is: {first}
>Numbering properties
> Autonumber format: .\t
> Else
>Numbering properties
> Autonumber format: .\t
>
> Else, if level is: 2
>If context is: ul
> Numbering properties
> Autonumber format: \b\t
>Else
> If context is: {first}
> Numbering properties
> Autonumber format: < >.\t
>Else
> Numbering properties
> Autonumber format: < >.\t
>
> On Tuesday, November 22, 2005 02:57 PM, Stacie Knas wrote:
>
> | Thank you for your kind replies. As I said, this is my
> | first EDD and there's a lot I don't know so please bear with
> | me. I set up the numbering in the EDD (I want to minimize
> | the available elements, and instead have the properties
> | governed by where they appear):
> |
> | If level is 1:
> |...
> | If context is: {first}
> | Numbering properties
> |Autonumber format: .\t
> | Else
> | Numbering properties
> |Autonumber format: .\t
> |
> | Else, if level is: 2
> | If context is: ul
> |Numbering properties
> | Autonumber format: \b\t
> | Else
> |If context is: {first}
> | Numbering properties
> | Autonumber format: .\t
> | Else
> |Numbering properties
> | Autonumber format: .\t
> |
> | There's more to it, of course. There is no opportunity in
> | the EDD won't let me put in a letter with a colon, n: or a:.
> | Hope this helps.
> |
> | I'm doing it the EDD way so that no matter where a LI
> | occurs, it will be formatted correctly depending on where it
> | is: numbered, bulleted, first, middle, table (haven't
> | figured that one out yet, had to create a new element and
> | para format), etc.
>
>
> - Lester
> ---
> Lester C. Smalley Email: lsmalley AT infocon DOT com
> Information Consultants, Inc. Phone: 302-239-2942 FAX: 302-239-1712
> Yorklyn, DE 19736Web: www.infocon.com
> ---
>
Numbered list item picks up from preceding nested list item
You can include the number or letter followed by a colon, you simply
type the desired text into the EDD as content of the "Autonumber Format"
element.
However, I believe that you really want instead of designating these
items as different numbering series (which is what the A: or N: do) you
should include an EmptyCounter building block (will display as < > )
before your existing counter. One empty counter should be used for each
level of nesting, so a second-level list (first nested list) has one, a
third level list has two, etc.
For example:
If level is 1:
...
If context is: {first}
Numbering properties
Autonumber format: .\t
Else
Numbering properties
Autonumber format: .\t
Else, if level is: 2
If context is: ul
Numbering properties
Autonumber format: \b\t
Else
If context is: {first}
Numbering properties
Autonumber format: < >.\t
Else
Numbering properties
Autonumber format: < >.\t
On Tuesday, November 22, 2005 02:57 PM, Stacie Knas wrote:
| Thank you for your kind replies. As I said, this is my
| first EDD and there's a lot I don't know so please bear with
| me. I set up the numbering in the EDD (I want to minimize
| the available elements, and instead have the properties
| governed by where they appear):
|
| If level is 1:
|...
| If context is: {first}
| Numbering properties
|Autonumber format: .\t
| Else
| Numbering properties
|Autonumber format: .\t
|
| Else, if level is: 2
| If context is: ul
|Numbering properties
| Autonumber format: \b\t
| Else
|If context is: {first}
| Numbering properties
| Autonumber format: .\t
| Else
|Numbering properties
| Autonumber format: .\t
|
| There's more to it, of course. There is no opportunity in
| the EDD won't let me put in a letter with a colon, n: or a:.
| Hope this helps.
|
| I'm doing it the EDD way so that no matter where a LI
| occurs, it will be formatted correctly depending on where it
| is: numbered, bulleted, first, middle, table (haven't
| figured that one out yet, had to create a new element and
| para format), etc.
- Lester
---
Lester C. Smalley Email: lsmalley AT infocon DOT com
Information Consultants, Inc. Phone: 302-239-2942 FAX: 302-239-1712
Yorklyn, DE 19736Web: www.infocon.com
---
Numbered list item picks up from preceding nested list item
Thank you for your kind replies. As I said, this is my first EDD and
there's a lot I don't know so please bear with me. I set up the
numbering in the EDD (I want to minimize the available elements, and
instead have the properties governed by where they appear):
If level is 1:
...
If context is: {first}
Numbering properties
Autonumber format: .\t
Else
Numbering properties
Autonumber format: .\t
Else, if level is: 2
If context is: ul
Numbering properties
Autonumber format: \b\t
Else
If context is: {first}
Numbering properties
Autonumber format: .\t
Else
Numbering properties
Autonumber format: .\t
There's more to it, of course. There is no opportunity in the EDD
won't let me put in a letter with a colon, n: or a:. Hope this helps.
I'm doing it the EDD way so that no matter where a LI occurs, it will
be formatted correctly depending on where it is: numbered, bulleted,
first, middle, table (haven't figured that one out yet, had to create
a new element and para format), etc.
On 11/22/05, Etzel, Gary wrote:
> I think you need to change the numbering properties for the paragraph
> format. I don't know if you are defining that through the paragraph designer
> or the EDD, but it's the same concept either way. In your first level OL,
> you probably have something like the following as the autonumber format:
> n:\t. In your second level OL, you need to change the n's to a different
> letter, like this: a:\t\t. That will distinguish the first-level "n"
> numbering scheme from the second level "a" numbering scheme.
>
> Regards,
>
> Gary
>
>
> -Original Message-
> From: framers-bounces+gary.etzel=advantica.biz at lists.frameusers.com
> [mailto:framers-bounces+gary.etzel=advantica.biz at lists.frameusers.com] On
> Behalf Of Stacie Knas
> Sent: Tuesday, November 22, 2005 1:27 PM
> To: framers at FrameUsers.com
> Subject: Numbered list item picks up from preceding nested list item
>
> Dear Framers:
>
> Frame 7.1, Windows XP Pro
>
> I am tweaking my first EDD (using the Structured Application
> Developer's Guide) to get the levels and spacing right with list items
> (LI) in ordered lists (OL) and unordered lists (UL) and various nested
> combinations thereof, including depending on whether the list is
> compact or non-compact. I am very pleased with what I have figured
> out so far, it's working well, except for one thing: If I have an OL
> nested in a LI in an OL, the LI that follows the nested OL picks up
> that OL's numbering, thus:
>
> 6. Item a
> 7. Item b
>
> a. item A
> b. item B
> c. item C
>
> 4. Item c
> 5. ...
>
> It doesn't happen with unordered lists. My level rules seem fine, and
> they work if they are not interrupted by a nested OL. I don't know
> where else to look; can you point me to places I could investigate?
> Thanks so much. This list is invaluable. Sorry I can't provide
> answers yet, but I'm learning a lot.
>
> --Stacie
> foolofgrace at gmail.com
> This e-mail, and any attachments are strictly confidential and intended for
> the addressee(s) only. The content may also contain legal, professional or
> other privileged information. If you are not the intended recipient, please
> notify the sender immediately, by return of email, and then delete the e-mail
> and any attachments. You should not disclose, copy or take any action in
> reliance on this transmission.
>
> Please ensure you have adequate virus protection before you open or detach
> any documents from this transmission.
>
> __
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> __
>
Re: Numbered list item picks up from preceding nested list item
This is great! I never noticed that "Empty Counter" entry before. I
followed your procedure, Lester, and it's perfecto! Thank you so
much. What a great list. Thank you all.
--Stacie
On 11/22/05, Lester C. Smalley <[EMAIL PROTECTED]> wrote:
> You can include the number or letter followed by a colon, you simply
> type the desired text into the EDD as content of the "Autonumber Format"
> element.
>
> However, I believe that you really want instead of designating these
> items as different numbering series (which is what the A: or N: do) you
> should include an EmptyCounter building block (will display as < > )
> before your existing counter. One empty counter should be used for each
> level of nesting, so a second-level list (first nested list) has one, a
> third level list has two, etc.
>
> For example:
>
> If level is 1:
>...
> If context is: {first}
>Numbering properties
> Autonumber format: .\t
> Else
>Numbering properties
> Autonumber format: .\t
>
> Else, if level is: 2
>If context is: ul
> Numbering properties
> Autonumber format: \b\t
>Else
> If context is: {first}
> Numbering properties
> Autonumber format: < >.\t
>Else
> Numbering properties
> Autonumber format: < >.\t
>
> On Tuesday, November 22, 2005 02:57 PM, Stacie Knas wrote:
>
> | Thank you for your kind replies. As I said, this is my
> | first EDD and there's a lot I don't know so please bear with
> | me. I set up the numbering in the EDD (I want to minimize
> | the available elements, and instead have the properties
> | governed by where they appear):
> |
> | If level is 1:
> |...
> | If context is: {first}
> | Numbering properties
> |Autonumber format: .\t
> | Else
> | Numbering properties
> |Autonumber format: .\t
> |
> | Else, if level is: 2
> | If context is: ul
> |Numbering properties
> | Autonumber format: \b\t
> | Else
> |If context is: {first}
> | Numbering properties
> | Autonumber format: .\t
> | Else
> |Numbering properties
> | Autonumber format: .\t
> |
> | There's more to it, of course. There is no opportunity in
> | the EDD won't let me put in a letter with a colon, n: or a:.
> | Hope this helps.
> |
> | I'm doing it the EDD way so that no matter where a LI
> | occurs, it will be formatted correctly depending on where it
> | is: numbered, bulleted, first, middle, table (haven't
> | figured that one out yet, had to create a new element and
> | para format), etc.
>
>
> - Lester
> ---
> Lester C. Smalley Email: lsmalley AT infocon DOT com
> Information Consultants, Inc. Phone: 302-239-2942 FAX: 302-239-1712
> Yorklyn, DE 19736Web: www.infocon.com
> ---
>
___
You are currently subscribed to Framers as [EMAIL PROTECTED]
To unsubscribe send a blank email to
[EMAIL PROTECTED]
or visit
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com
Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.
Numbered list item picks up from preceding nested list item
Dear Framers: Frame 7.1, Windows XP Pro I am tweaking my first EDD (using the Structured Application Developer's Guide) to get the levels and spacing right with list items (LI) in ordered lists (OL) and unordered lists (UL) and various nested combinations thereof, including depending on whether the list is compact or non-compact. I am very pleased with what I have figured out so far, it's working well, except for one thing: If I have an OL nested in a LI in an OL, the LI that follows the nested OL picks up that OL's numbering, thus: 6. Item a 7. Item b a. item A b. item B c. item C 4. Item c 5. ? It doesn't happen with unordered lists. My level rules seem fine, and they work if they are not interrupted by a nested OL. I don't know where else to look; can you point me to places I could investigate? Thanks so much. This list is invaluable. Sorry I can't provide answers yet, but I'm learning a lot. --Stacie foolofgrace at gmail.com
RE: Numbered list item picks up from preceding nested list item
You can include the number or letter followed by a colon, you simply
type the desired text into the EDD as content of the "Autonumber Format"
element.
However, I believe that you really want instead of designating these
items as different numbering series (which is what the A: or N: do) you
should include an EmptyCounter building block (will display as < > )
before your existing counter. One empty counter should be used for each
level of nesting, so a second-level list (first nested list) has one, a
third level list has two, etc.
For example:
If level is 1:
...
If context is: {first}
Numbering properties
Autonumber format: .\t
Else
Numbering properties
Autonumber format: .\t
Else, if level is: 2
If context is: ul
Numbering properties
Autonumber format: \b\t
Else
If context is: {first}
Numbering properties
Autonumber format: < >.\t
Else
Numbering properties
Autonumber format: < >.\t
On Tuesday, November 22, 2005 02:57 PM, Stacie Knas wrote:
| Thank you for your kind replies. As I said, this is my
| first EDD and there's a lot I don't know so please bear with
| me. I set up the numbering in the EDD (I want to minimize
| the available elements, and instead have the properties
| governed by where they appear):
|
| If level is 1:
|...
| If context is: {first}
| Numbering properties
|Autonumber format: .\t
| Else
| Numbering properties
|Autonumber format: .\t
|
| Else, if level is: 2
| If context is: ul
|Numbering properties
| Autonumber format: \b\t
| Else
|If context is: {first}
| Numbering properties
| Autonumber format: .\t
| Else
|Numbering properties
| Autonumber format: .\t
|
| There's more to it, of course. There is no opportunity in
| the EDD won't let me put in a letter with a colon, n: or a:.
| Hope this helps.
|
| I'm doing it the EDD way so that no matter where a LI
| occurs, it will be formatted correctly depending on where it
| is: numbered, bulleted, first, middle, table (haven't
| figured that one out yet, had to create a new element and
| para format), etc.
- Lester
---
Lester C. Smalley Email: lsmalley AT infocon DOT com
Information Consultants, Inc. Phone: 302-239-2942 FAX: 302-239-1712
Yorklyn, DE 19736Web: www.infocon.com
---
___
You are currently subscribed to Framers as [EMAIL PROTECTED]
To unsubscribe send a blank email to
[EMAIL PROTECTED]
or visit
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com
Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.
Re: Numbered list item picks up from preceding nested list item
Thank you for your kind replies. As I said, this is my first EDD and
there's a lot I don't know so please bear with me. I set up the
numbering in the EDD (I want to minimize the available elements, and
instead have the properties governed by where they appear):
If level is 1:
...
If context is: {first}
Numbering properties
Autonumber format: .\t
Else
Numbering properties
Autonumber format: .\t
Else, if level is: 2
If context is: ul
Numbering properties
Autonumber format: \b\t
Else
If context is: {first}
Numbering properties
Autonumber format: .\t
Else
Numbering properties
Autonumber format: .\t
There's more to it, of course. There is no opportunity in the EDD
won't let me put in a letter with a colon, n: or a:. Hope this helps.
I'm doing it the EDD way so that no matter where a LI occurs, it will
be formatted correctly depending on where it is: numbered, bulleted,
first, middle, table (haven't figured that one out yet, had to create
a new element and para format), etc.
On 11/22/05, Etzel, Gary <[EMAIL PROTECTED]> wrote:
> I think you need to change the numbering properties for the paragraph
> format. I don't know if you are defining that through the paragraph designer
> or the EDD, but it's the same concept either way. In your first level OL,
> you probably have something like the following as the autonumber format:
> n:\t. In your second level OL, you need to change the n's to a different
> letter, like this: a:\t\t. That will distinguish the first-level "n"
> numbering scheme from the second level "a" numbering scheme.
>
> Regards,
>
> Gary
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Stacie Knas
> Sent: Tuesday, November 22, 2005 1:27 PM
> To: framers@FrameUsers.com
> Subject: Numbered list item picks up from preceding nested list item
>
> Dear Framers:
>
> Frame 7.1, Windows XP Pro
>
> I am tweaking my first EDD (using the Structured Application
> Developer's Guide) to get the levels and spacing right with list items
> (LI) in ordered lists (OL) and unordered lists (UL) and various nested
> combinations thereof, including depending on whether the list is
> compact or non-compact. I am very pleased with what I have figured
> out so far, it's working well, except for one thing: If I have an OL
> nested in a LI in an OL, the LI that follows the nested OL picks up
> that OL's numbering, thus:
>
> 6. Item a
> 7. Item b
>
> a. item A
> b. item B
> c. item C
>
> 4. Item c
> 5. ...
>
> It doesn't happen with unordered lists. My level rules seem fine, and
> they work if they are not interrupted by a nested OL. I don't know
> where else to look; can you point me to places I could investigate?
> Thanks so much. This list is invaluable. Sorry I can't provide
> answers yet, but I'm learning a lot.
>
> --Stacie
> [EMAIL PROTECTED]
> This e-mail, and any attachments are strictly confidential and intended for
> the addressee(s) only. The content may also contain legal, professional or
> other privileged information. If you are not the intended recipient, please
> notify the sender immediately, by return of email, and then delete the e-mail
> and any attachments. You should not disclose, copy or take any action in
> reliance on this transmission.
>
> Please ensure you have adequate virus protection before you open or detach
> any documents from this transmission.
>
> __
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> __
>
___
You are currently subscribed to Framers as [EMAIL PROTECTED]
To unsubscribe send a blank email to
[EMAIL PROTECTED]
or visit
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com
Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.
Numbered list item picks up from preceding nested list item
Dear Framers: Frame 7.1, Windows XP Pro I am tweaking my first EDD (using the Structured Application Developer's Guide) to get the levels and spacing right with list items (LI) in ordered lists (OL) and unordered lists (UL) and various nested combinations thereof, including depending on whether the list is compact or non-compact. I am very pleased with what I have figured out so far, it's working well, except for one thing: If I have an OL nested in a LI in an OL, the LI that follows the nested OL picks up that OL's numbering, thus: 6. Item a 7. Item b a. item A b. item B c. item C 4. Item c 5. … It doesn't happen with unordered lists. My level rules seem fine, and they work if they are not interrupted by a nested OL. I don't know where else to look; can you point me to places I could investigate? Thanks so much. This list is invaluable. Sorry I can't provide answers yet, but I'm learning a lot. --Stacie [EMAIL PROTECTED] ___ You are currently subscribed to Framers as [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
