# 2024.04.02 Weekly Meeting

**URL:** <https://discourse.slicer.org/t/2024-04-02-weekly-meeting/35204>\
**Category:** Weekly meetings\
**Created:** [April 1, 2024, 5:41pm UTC](https://discourse.slicer.org/t/2024-04-02-weekly-meeting/35204 "2024-04-01T17:41:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sam\_Horvath](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/sam_horvath/32/3092_2.png) [@Sam\_Horvath](https://discourse.slicer.org/u/Sam_Horvath)\
**Post date:** [April 1, 2024, 5:41pm UTC](https://discourse.slicer.org/t/2024-04-02-weekly-meeting/35204/1 "2024-04-01T17:41:08Z")

</div>

Tomorrow, we will be having our next weekly hangout at **10:00 AM ET until 11:00 AM ET**.

Anyone is welcome to join at this link: [https://bit.ly/slicer-googlemeet-hosted-by-kitware](https://bit.ly/slicer-googlemeet-hosted-by-kitware)

* * *

> **Weekly Meeting**
>
> **Starts:** April 2, 2024, 10:00am (America/New\_York)\
> **Link:** <https://bit.ly/slicer-googlemeet-hosted-by-kitware>

**Agenda:**

Please post to this thread to put a topic on the agenda! We will try to prioritize agenda items during the meeting.

* * *

Thanks  
Sam and J-Christophe

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [April 1, 2024, 9:20pm UTC](https://discourse.slicer.org/t/2024-04-02-weekly-meeting/35204/2 "2024-04-01T21:20:58Z")

</div>

I’d like to discuss this issue: [GrayscaleModelMaker geometry incorrect in 5.6.1 but works in preview · Issue #7668 · Slicer/Slicer · GitHub](https://github.com/Slicer/Slicer/issues/7668)

---

<div class="post-metadata">

**Author:** ![wenples](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/wenples/32/6801_2.png) [@wenples](https://discourse.slicer.org/u/wenples)\
**Post date:** [April 2, 2024, 1:04pm UTC](https://discourse.slicer.org/t/2024-04-02-weekly-meeting/35204/3 "2024-04-02T13:04:45Z")

</div>

If there is time today, I’d love to go over new icon designs, palettes, theme/state changing approach and where to find this info on github. Would be great time to request any underlying changes to palette or approach, while it’s still easy to make retro changes to existing designs, and lock things in before taking on Slice viewers and core module icons!

Cheers,  
wen

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [April 2, 2024, 3:27pm UTC](https://discourse.slicer.org/t/2024-04-02-weekly-meeting/35204/4 "2024-04-02T15:27:01Z")

</div>

## Meeting notes

- Reviewed new icon designs, palettes, theme/state changing approach

- [PR-7668](https://github.com/Slicer/Slicer/issues/7668): GrayscaleModelMaker geometry incorrect in 5.6.1 but works in preview

- Slicer Telemetry

- New developer questions

- [Isssue-7206](https://github.com/Slicer/Slicer/issues/7206): Segment visibility in slice views can become out-of-sync with current visibility state

---

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [April 2, 2024, 11:28pm UTC](https://discourse.slicer.org/t/2024-04-02-weekly-meeting/35204/5 "2024-04-02T23:28:41Z")

</div>

> [@jcfr](#):
>
> Next: Create Slicer 5.6.2 release. See [Slicer 5.6.2 Milestone · GitHub](https://github.com/Slicer/Slicer/milestone/11)

Since there is planned patch release, can you also incorporate the transform issue fix? I don;t think that’s fixed for 5.6.

> <https://github.com/Slicer/Slicer/pull/7594>
>
> This is a fix for the transformation matrix editing glitch that @RafaelPalomar d…emonstrated during the weekly developer meeting.
> 
> In transforms module, when linear transformation matrix values were edited using spinboxes and then by directly editing the matrix, the value that was previously edited in the spinbox got overwritten by the new value.
> 
> The issue was that a single slot was used for all signals coming from all sliders and in the slot implementation the active focus was used to determine which axis should be updated. Fixed by using a separate slot for each axis. This way we don't rely on the GUI widget focus, which may go through complex transitions during transform editing using various widgets.