Skip to content
代码片段 群组 项目
  1. 12月 14, 2023
  2. 12月 12, 2023
    • Olivier Goffart's avatar
      Compiler: Error when assigning to compile time properties · 5d4c390b
      Olivier Goffart 创作于
      Some property need to be known at compile time. We already had checks
      that the binding is a compile time constant, but there was no check to
      prevent, say
      
          self.row = 42;
      
      which wouldn't work or could even cause panic or miscompilation of
      generated code
      
      Closes #4037
      5d4c390b
  3. 12月 11, 2023
  4. 12月 08, 2023
  5. 12月 07, 2023
  6. 12月 01, 2023
  7. 11月 30, 2023
  8. 11月 29, 2023
  9. 11月 28, 2023
  10. 11月 27, 2023
  11. 11月 23, 2023
  12. 11月 22, 2023
  13. 11月 10, 2023
  14. 11月 07, 2023
  15. 11月 03, 2023
  16. 10月 31, 2023
    • Olivier Goffart's avatar
      Models: fix writing data doesn't update ListView model data property · d55803d2
      Olivier Goffart 创作于
      This fixes a couple of bug:
       - Bug #3740 happens because `Repeater::model_set_row_data` did not use
         the inner.offset to get the instance (So that's the `val == 106` part
         of the test)
       - But I went ahead and also tested what happenned if you changed the
         model from the "outside" using the `model[i] = `, and that was not
         implemented, hence the move of the code from
         `Repeater::model_set_row_data` to `RepeaterTracker::row_changed`,
         That does need Pin though, so Pin was added everywhere
       - C++ is not affected by bug #3740, because because the C++ listview
         don't do the "allocate only visible" optimization. But the
         "val == 1106" part of the test would fail so this patch also moces
         the update from  `model_set_row_data` to `row_changed`.
         But following that we don't set the state as Dirty in `row_changed`,
         the write_to_model test started filling  because the `row_added`
         function was missing an update of the index on every further items
      
      The change in the interpreter prevent a borrow_mut from causing trouble.
      The Value really don't need to be in a RefCell anyway
      
      Fix #3740
      d55803d2
  17. 10月 26, 2023
    • Olivier Goffart's avatar
      Improve the slint! macro with rust-analyzer with `-` · c51fb14a
      Olivier Goffart 创作于
      We currently use the debug representation of Span to know if they are
      next touching eachother as there are no stable way currently.
      But that doesn't work with rust analyzer as it doesn't have a
      representation we can test.
      Also Span::source_text is not implemented with rust analyzer.
      
      So just default to identifier with `-` touching instead of not touching
      as this happens more often.
      
      One can still use `(foo)-(bar)` when one really need minus
      
      CC #685
      c51fb14a
  18. 10月 23, 2023
  19. 10月 19, 2023
  20. 10月 17, 2023
  21. 10月 13, 2023
  22. 10月 11, 2023
  23. 10月 10, 2023
  24. 10月 07, 2023
  25. 10月 06, 2023
  26. 10月 02, 2023
  27. 9月 29, 2023