Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • This is a great post and what I really like about it is how it takes the battle to the "GUIs are useless" crowd (though I don't believe you intended this). By having direct, first-hand experience with user interaction, what you're pointing out repeatedly is that just because something is "correct" doesn't mean that it satisfies user expectations/needs. That's a point that the "CLI only" crowd often seems to miss.

    In any event, thanks for explaining this.

    • Not really. As part of the splinter group "GUIs should be useless, because I dislike needing to use them" crowd, I feel I understand enough of what the "GUIs are useless" crowd thinks to confidently state, this would, at best, tell them y'all are finally concerned with *some* of the right things, but you still have a long way to come.

      However, they'd more likely skim, and come away with the overall impression that GUIs are bad and prone to flicker - nothing they didn't already know.

  • I think you've handled part of the issue very well. For all I know, you've already handled the other part that this post suggests exists. However, some of your post suggests otherwise.

    Here, you're focused on what happens to refresh requests while Padre is in the process of changing data that will inappropriately show if that refresh request is immediately honored.

    What about what happens to a refresh request to something that has not changed? For example, we get a global refresh request, and the file wind

    • The locking system itself will satisfactorily take care of duplicate refresh requests, because each element that can be refreshed has a method, and each method is just in a boolean state.

      There's some nigglies remaining, but the basics already work.

      Dirty flagging is a possibility, but not something we're doing at the moment.

      We assume that if someone said we needed to refresh, then we really did need to. And with improved locking, we can rely on the caller a bit more to give us more accurate instructions on w