I’m working on a project that needs lots of toolbars on screen at once, even though not all of them will be used at the same time. So, I’m modelling this ‘foldable’ dock widget after what I remember Photoshop panels used to be like.

It’s a work in progress, but would like to hear constructive suggestions.

https://blocks.programming.dev/0101100101/42c5d67f86c049baa3500aa38e439f8a

  • logging_strict@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    2 days ago

    self.float_button.setIcon is a Python wrapper around a C++ library. Might not be possible to, or want to, step into the function.

    if foo or bar is part of a if-else condition. The else portion needs # pragma: no cover or coverage may complain.

    • FizzyOrange@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      17 hours ago

      Well… the else condition (bar) needs to be covered. I haven’t used branch coverage tools in Python but in any sane language you cover the actual semantics, not the lines. It shouldn’t make any difference if you write your code on one line, or with ternary expressions, or whatever.

      • logging_strict@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        16 hours ago

        What matters is what the package coverage can do and what limitations or nuances it has. Have to work with what we have. We are lucky to have coverage. Especially within a subprocess and multiprocessing workers

      • logging_strict@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        16 hours ago

        We are dealing with Python and coverage, not some theoretical situation or circumstances.

        Was assuming measuring branch coverage. In which case, my advice is coming from experience