Re: scrolling, and losing keyboard input

On Thursday 13 March 2008 16:46, Arlo Leach wrote:
> Hello,
>
> I started using Amaya a month ago after looking for a replacement for
> Dreamweaver. I'm happy to say I've built several websites since then and
> haven't opened Dreamweaver once! Amaya has its quirks, but so does
> Dreamweaver, and Amaya has some unique features to balance that out. I've
> been telling everyone about Amaya and am planning a class to teach new
> users about it.
>
> However, a couple issues have been driving me crazy recently:
>
> - Clicking in the scroll bar, above or below the thumb, should scroll my
> document by one screen at a time. This works inconsistently for me;
> sometimes a click won't scroll at all, sometimes it will scroll several
> screens, and sometimes the document display will become garbled so that I
> won't know where it has scrolled to (until I click the document and the
> display clears up).

Hum, normally clicking on a position in the scrollbar skip to the position in 
the document . As Amaya doesn't have the whole document formatted (often too 
big), it re-formats the requested part. But often the position is not exactly 
the same and it seems inconsistent.
We could limit the move to one screen up or down if you think it's the habit 
on MacOS

> - I will regularly lose the ability to make keyboard input in the main
> document view -- if I press a letter key, nothing happens. I can still use
> keyboard shortcuts like command-c and command-s. 

Perhaps that occurs after a specific operation. If you have a scenario that 
shows the bug, we'll be happy to fix the problem.
For the moment we're not able to reproduce it. We continue to investigate.

> Also, the escape key does 
> not work to select the current tag, but the F2 key does.

Esc is sometimes kept by the window manager.

> If I switch to 
> source view I can type normally, but if I return to the document view the
> character input is still disabled.

> I haven't been able to isolate an action 
> that drops the keyboard input, and the only solution I've found is to quit
> and relaunch the application. This happens to me at least once an hour and
> sometimes after just a few minutes of using the application.
>
> Are these known issues, and are there any plans to address them?
>
> I'm using the Feb. 29 release on an Intel MacBook Pro with Mac OS 10.5.2.
>
> Thanks,
> -Arlo
>
> _______________________________
>
> Arlo Leach
> 773.769.6106
> http://arlomedia.com
>
> Make friends with your computer
> http://compyschool.com

-- 
Irène Vatton @ INRIA Rhône-Alpes

Received on Monday, 17 March 2008 13:27:40 UTC