in reply to Very strange Scrollbar behavior in Win32 Perl/Tk version 804.027

actually my wrong yesterday reply is not wrong here.

The scrollbar button size problem *is* well known and fixed in Tk version 8.5.

BTW why you keep pointing you're on Win32? Perl is so crossplatform!
I mean - if you figure out cross-platform differences between perl behaviour (behaves here but misbehaves elsewhere) - then yes, start pointing the $^O.

BTW I sometimes use WinCE but often am silent about that
:) :) :)

  • Comment on Re: Very strange Scrollbar behavior in Win32 Perl/Tk version 804.027

Replies are listed 'Best First'.
Re^2: Very strange Scrollbar behavior in Win32 Perl/Tk version 804.027
by GrandFather (Saint) on Oct 29, 2006 at 22:49 UTC

    Platform information is often useful up front because Perl is cross-platform and people who only use a single platform are often unaware that a problem may be isolated to their context. At the very least others can then report reproducing the problem (or not) and possibly start narrow the scope of the problem.

    Many things are not platform sensitive. However GUI and file system related things very often are. A brief heads up in those cases saves time for the OP and for whomever may be replying.

    Version information is always useful up front where buggy behaviour is being reported.


    DWIM is Perl's answer to Gödel
Re^2: Very strange Scrollbar behavior in Win32 Perl/Tk version 804.027
by Bro. Doug (Monk) on Oct 30, 2006 at 02:32 UTC
    The platform does, in fact, make a difference.

    To briefly cite some specific examples:

    1> Perl/Tk's fileevent handler doesn't work in Windows.
    2> caller() doesn't return the proper line number on all Windows machines.
    3> print SCK $stuff doesn't work on the E-Machines T2862 but seems to work just fine on other models of E-Machines ( a severely aggravating problem ).

    Ideally, cross-platforming works perfectly. Unfortunately, the world ain't ideal.

    Peace, monks.

    Bro. Doug :wq
      all true, but platform difference should be minimal, and somewhat platform-specific.

      When speaking on non-platform specific GUI element, it should behave everywhere consistently, that is why first attention should be paid to logic and widget, and only afterwards we should consider whether misbehaviour is $^O-specific!

      BTW I've never thought of Perl/Tk's fileevent as non-working on Windows
      Did you encountered difficulties with it?

        Yes. I've had some terrrible problems with fileevent.

        Setting one up has caused my socketeering programs to hang indefinitely. I tried several different ways of opening the socket before passing it to fileevent for read/write polling, but got the same behaviour everytime. Then I hit the web (it was before my days on PerlMonks) and found a few references to "We're working on fixing this! It's broke on Windows!" At said point, I wrote a $mw->repeat to accomplish c-style polling.

        Perhaps in the near future I'll present this problem to the monks. It seems a good idea...

        Peace, monks. I'm off to work.

        Bro. Doug :wq