and switching to getOpenFile for file selection.
That seems very odd, as it seems to destroy the purpose behind the module , which is to avoid getOpenFile by implementing a different look/feel...
Uhm, I'm not sure I I'd miss something here. Where do you get the information that Tk::FileEntry uses the far ugliest file selector on purpose?
I thought it's used because at the time when the module was written, there was no getOpenFile implementation for all OS'.
So, if this is not the case and Tk::FileEntry will be stuck with this scarecrow dialog, then my patch (which did not get any attention) was absolutely obsolete and I will have to do it myself anyway.
What do you think of Tk::FilePicker?
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link
or How to display code and escape characters
are good places to start.