Re: TK: How to change color of readonly BrowseEntry

[Anonymous Monk]

in reply to SOLVED - TK: How to change color of readonly BrowseEntry

Win32::GUI has some odd behavior. For example, all of my widgets start with a flat "XP" style, but one of them changes to the older indented style when I change values in a completely different widget.

Hmm, sounds fishy :) but I've seen weirder :)

How could they not notice that problem?

Because it isn't much of a problem :)

Checking perl version is the wrong way to check for File::Spec version, File::Spec had a verion number even in 5.005 in 1998 :)

General lack of documentation. Far too many entries are simply TBD for my taste.

It has way too much documentation if you ask me :) Its just a thin wrapper around MFC, all the real documentation is on MSDN, how things should be have, all that

[mrider]

Considering that the module doesn't work unless one edits that line - I'd say it's a problem...

PLUS, all they have to do is download the module and install/use it once. It'll frikkin jump out and bite them on the donkey!

[Anonymous Monk]

Considering that the module doesn't work unless one edits that line - I'd say it's a problem...

Oh really? http://cpansearch.perl.org/src/ROBERTMAY/Win32-GUI-1.06/Win32-GUI-BitmapInline/BitmapInline.pm

    if($[ < 5.008000) {
        $tmpfile =~ /^(.*)$/;
        $tmpfile = $1;
    }

So it always untaints $1, I don't see how that could break anything

PLUS, all they have to do is download the module and install/use it once. It'll frikkin jump out and bite them on the donkey!

This is why you ought to make life easy :) make your own distribution :) its easy

[mrider]

Let me get this straight: You're seriously suggesting that I maintain my own distribution because the author can't be arsed to test their own module?

I don't think so...

 

 

Apparently I can't reply to the reply below, it will be too deep of a level. So I'll reply here:

(A.M.)Yup, I think so. You are the author now. You should ship working software, not task your users to read a readme then install and hand-edit some module.

In case you missed this point in the original question - this is an internal use only reporting tool. My users won't even know what programming language I'm using, and the users don't have permissions to install software at all. The "instructions" would be if someone needed to duplicate my development environment, not instructions for my users.

 

 

(A.M.)There really is no maintenance, besides the maintenance you do already (installing modules on your dev machine), after than its a one or two clicks and you're uploading your own binary release with the latest version from your dev machine

The level of difficulty is totally beside the point. The original author has left the code in place with a stupid effing mistake for who knows how long. Additionally, the author has a number of outstanding bugs that aren't even being addressed or looked at. Pretty much not a situation that engenders a feeling that this is something I want to maintain myself.

TLDR: No chance that's happening. Not a chance in hades.