Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • 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 which specific areas to refresh.

      In addition, each refresh method is welcome to establish whether or not they are able to shortcut.

      As for the actual painting, we don't really get involved at that level. We merely issue changes to the windowing toolkit.

      One thing I have noticed on my machine, is that in some cases flickering seems to be appearing even on areas we AREN'T updating. But for right now I'm just happy that changes to application state are running at three to five times faster than they were before, and I'll look into the rest in the next round of speed improvments.