jamovi

Hi all, the blog post introducing the module is now up here:
https://blog.jamovi.org/2026/07/09/summarytables.html

I also thought it was a bug, the design is a little confusing for my eyes

Also, seems the release notes page is down
https://www.jamovi.org/release-notes.html

jonathon wrote: Wed May 27, 2026 11:25 pm when you're ready nour, consider writing a blog post:

https://blog.jamovi.org/

cheers

Thanks, Jonathon! I would!

Hi everyone,

I am happy to introduce a new module available in the jamovi library: SummaryTables .

A comprehensive module for creating publication-ready summary and regression tables in jamovi, powered by gtsummary package in R. Please note that it requires jamovi version 2.7.12 or later.

Here ...

so sorry for that, I did use ai to summarize my main points since it was too long, it seems it made it worse

For the `.27` version, the link above not working and giving me this error :
"404 - Page not found!
Sorry, that page doesn’t exist.

We’ll redirect you to the main page in a few seconds, and ...

Hi Jonathon,

Thank you so much for the incredibly quick turnaround on this! That is exactly what I was hoping for.

I'm using Windows 11. I would really appreciate a pre-release version so I can test the fix and continue development. I will make sure to add `minApp: 2.7.27` to our `0000.yaml ...

Hi Jonathon,

On the drag-resize concern:

I understand the concern. Looking at fromProtoBuf in image.R, the width and height in the protobuf are the full dimensions (already including whatever scale the client applied), and they are restored unconditionally:

private$.width <- image$width ...

Hi Jonathon,

Thanks for looking into it.

I get why dropping the size check globally feels wrong. You wouldn't want to break the invalidation rules for standard images.

What do you think about an opt-in flag? Maybe adding a property like dynamicSize: true to the YAML for the Image element. If that ...

Hi Jonathon,

Sorry, I think I complicated my first reply. Let me simplify.

You may remember the GitHub issue where I asked about dynamically sizing images. You suggested the .postInit + .run pattern:

- In .run(), calculate the size, call setSize(), and cache the dimensions in a hidden element ...

Hi Jonathon,

Thanks for the quick reply. I traced the issue and it only affects images that use setSize() in .run() (dynamically sized images). Fixed-size images (width/height set in the YAML) work fine.

What happens

When clearWith does not trigger, fromProtoBuf in image.R still clears filePath ...