Re: PERL Interpreter Preferences bug

Hi Keith,

I can duplicate this by "crawling behind the covers", setting
the "perlDefaultInterpreter" pref to null (using JavaScript),
and then making a different change in the prefs UI.  We typically
don't validate settings made outside the UI, like in a macro
or extension.  Can you reproduce the steps to get into this
situation?   Do you see this bug repeatedly?  What was the
value in the Perl prefs page when the bug occurs -- is it
blank?

Can you reproduce this problem?

Also, what's in the pystderr.log file when this occurs?

- Eric

On 10/7/2009 9:31 AM, J. Keith Chant wrote:
> Has anyone else seen this?
>
> When I open the preferences page - if I click into the Languages ->  Perl, then
> click into another menu item without changing anything on the Perl options -
> when I click OK to close the preferences I get an alert:
> "No Perl interpreter could be found at 'None'. You must make another selection
> for the default Perl interpreter."
>
> If I go back to the Perl language options and change the interpreter to "Find on
> path" in the dropdown I can now close the preference window.
>
> Just wondering why it is doing this.
>
> Thanks,
> Keith
>
>
> _______________________________________________
> Komodo-discuss mailing list
> [email protected]
> To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
> Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss
_______________________________________________
Komodo-discuss mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss