Since I never work that way, I can't report whether it was there in 2K2
on my computer, but I just tried what I think was outlined using 2K3 and
my note entry is just as it should be.
Mark D. Lew wrote:
> At 2:10 PM 07/17/02, Johannes Gebauer wrote:
>
>
>>He means using MassMover, select
At 2:10 PM 07/17/02, Johannes Gebauer wrote:
>He means using MassMover, select a measure in page view and "move" it to the
>next system using the cursor-down key.
Aha, I get it now. I do use that function sometimes, if I make a layout
adjustment after I've locked my systems. But I tend to thin
on 7/17/02 7:10 AM, Johannes Gebauer at [EMAIL PROTECTED] wrote:
> On 17.07.2002 14:19 Uhr, Mark D. Lew wrote
>
>>> Here's how to create the bug:
>>>
>>> 1. Open a template with multiple systems on the same page and with spacing
>>> such as the above mentioned "Piano Grand Staff" and go to page
On 17.07.2002 14:19 Uhr, Mark D. Lew wrote
>> Here's how to create the bug:
>>
>> 1. Open a template with multiple systems on the same page and with spacing
>> such as the above mentioned "Piano Grand Staff" and go to page view.
>>
>> 2. Move at least one measure to an adjacent system on the pa
At 1:20 AM 07/17/02, Don Hart wrote:
>Here's how to create the bug:
>
>1. Open a template with multiple systems on the same page and with spacing
>such as the above mentioned "Piano Grand Staff" and go to page view.
>
>2. Move at least one measure to an adjacent system on the page.
>
>3. Select t
on 7/16/02 2:34 AM, Mark D. Lew at [EMAIL PROTECTED] wrote:
> At 10:12 AM 07/15/02, Jari Williamsson wrote:
>
>> Not correct, it's specific to in which order you enter things and what's in
>> the file. The bug appears in Windows as well and can be reproduced by
>> sending in a file with the file
At 04:07 PM 7/16/02 -0400, Burt Fenner wrote:
[re pitch displacement bug]
>This does not happen in WinFin2003.
It still happens for me WinF2K3. I had hoped it was cured. :(
(But it was a file imported from F2K2. Maybe a native F2K3 file is different.)
Dennis
__
- Original Message -
From: "Mark D. Lew" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, July 16, 2002 3:34 AM
Subject: Re: [Finale] Bug in Speedy Entry (2002b)
> Interesting. I got the distinct impression that the pro
At 10:12 AM 07/15/02, Jari Williamsson wrote:
>Not correct, it's specific to in which order you enter things and what's in
>the file. The bug appears in Windows as well and can be reproduced by
>sending in a file with the file state appearing something like 5 editing
>steps before the bug appeare
Mark D. Lew writes:
> Evidently this bug only occurs under certain unusual circumstances in the
> overall environment, which is why only a few of us have experienced it (all
> on older Macs, I believe).
Not correct, it's specific to in which order you enter things and what's in
the file. The b
[CC'ed to tech support; consider removing if using "reply to all".]
At 9:50 PM 07/14/02, Michael Lawlor wrote:
>There is a problem I encounter occasionally, using the computer keyboard
>with speedy entry, where a note will appear an octave and a sixth higher
>than entered. Depending on how this
Michael Lawlor writes:
> There is a problem I encounter occasionally, using the computer keyboard
> with speedy entry, where a note will appear an octave and a sixth higher
> than entered. Depending on how this has been done determines how easy it is
> to fix, but is it a known problem and is th
There is a problem I encounter occasionally, using the computer keyboard
with speedy entry, where a note will appear an octave and a sixth higher
than entered. Depending on how this has been done determines how easy it is
to fix, but is it a known problem and is there a solution.
Michael Lawlor
There is a problem I encounter occasionally, using the computer keyboard
with speedy entry, where a note will appear an octave and a sixth higher
than entered. Depending on how this has been done determines how easy it is
to fix, but is it a known problem and is there a solution.
Michael Lawlor
14 matches
Mail list logo
