<html>
    <head>
      <base href="https://bugs.documentfoundation.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_UNCONFIRMED "
   title="UNCONFIRMED - Try to not use SfxItemState::UNKNOWN in preparation of refactoring of ItemSet/ItemPool"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=130428">130428</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Try to not use SfxItemState::UNKNOWN in preparation of refactoring of ItemSet/ItemPool
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>LibreOffice
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>UNCONFIRMED
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>enhancement
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>LibreOffice
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>libreoffice-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>Armin.Le.Grand@me.com
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Background: I do experiment actively with a much simplified, type-safe ersion
of ItemSet/ItemPool to make it easier for everyone to deal with these, still
keeping performance and mem footprint. Stumbled over
SfxItemState::SfxItemState::UNKNOWN which is in the way for that
simplifications. Looking for a way around it relealed that it might bne hard
and take off quite some of the 'easier' portion, so I'll try to remove it's
usages as much as possible.
Im most cases these usages (127) are about checking if that Item is 'known' at
the SfxItemSet which uses the info of the defined ranges at these - mostly in
UI stuff (anyways a 2nd ItemSet use that is kinda 'hacky') to hide controls.
I will try to replace usages with what really is intended and protocol it here.
This might lead to some changes in the core that hopefully will do no harm, but
to be able to revert thede and maybe cancel that try here again will not all
here</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>