[Padre-dev] Next release on Saturday/Sunday

[Gabor Szabo]

On Fri, Jan 2, 2009 at 3:26 PM, Petar Shangov <pshangov at yahoo.com> wrote:
> ----- Original Message ----
>
>> From: Gabor Szabo <szabgab at gmail.com>
>> To: Padre development discussion list <padre-dev at perlide.org>
>> Sent: Thursday, 1 January, 2009 21:14:04
>> Subject: [Padre-dev] Next release on Saturday/Sunday
>
>>
>> 4) Show Error List is checked in the menu but the relevant notebook
>> does not show up at start up
>>     (Selecting the menu option twice opens the window)
>
> Error List would not show unless the Output window is already shown. I committed a fix, but I am not sure this is exactly the bug you are talking about. Can you check now and tell me if it is still a problem? If so, when does it happen? Which other tabs in the bottom pane are shown when Error List fails to show?

no. The issue is that while both "Show Output" and "Show Error List"
are checked when I start Padre only the Output pane
shows up.


>
>> 5) While Error list is checked if I try to run the script
>> t/files/hello_with_warn.pl
>>      using F5 I get the following error on STDERR:
>> Undefined subroutine &Parse::ErrorString::Perl::transmo called at
>> /home/gabor/perl5lib/lib/Parse/ErrorString/Perl.pm line 373.
>
> Unfortunately I cannot replicate this. Do other people get this error message too? Can you try and run 'splain' on the error output from hello_with_warn.pl and tell me if it parses it OK?


The problem as far as I can understand is that transmo() function is generated
in a Task and it is not available when the code is trying to call it.

>
>> 6) my new F1 key binding now hides that of the error window
>
> The quickest solution will of course be to replace the F1 key with some other shortcut. Can you tell me which F keys are not taken yet? If someone can think of a more elegant GUI solution you are welcome to suggest, and I'll try to implement it.

The whole reason for changing the key binding was to make both bind to F1 :-)
So yes, switching back would solve the issue for now but we should be
able to let the specific
windows handle F1 by themselves when they are in focus.

Gabor