jamovi

thanks for letting us know.

fixed now.

jonathon

drop us a line at contact <at> jamovi.org, if you're interested in adding this to the library.

good to review best practices here if you haven't already.

https://dev.jamovi.org/

jonathon

hi, the translations are performed by volunteers, and we're not really in the position to adjudicate what is the best spanish term ("buscamos autobus terminal" is about the extent of my espanol), but we can certainly introduce a review step if there's someone willing to be the reviewer. dr...

we pushed out the 2.7.30 last night ... we'll give it a day or two for the dust to settle, and then we'll move it across to 'solid'.

cheers

jonathon

It sounds like you're using a particular module. Could tell us what module you're using?

Jonathon

it would be worth seeing if vincent of vijPlots might add something like this.

jonathon

sorry for the stuff around. you'll find the 2.7.27 available from the download page.

cheers

ugh ... too much AI slop ... 1. it would be surprising if a dummy model and plot would take a whole second to produce 2. you don't need to display it. 3 ... maybe ... but none of this matters because we're going a different route. here's the .27 https://www.jamovi.org/downloads/jamovi-2.7.27.0-win-x...

i've made the following changes. https://github.com/jamovi/jamovi/commit/f1bce8aca5d4d9d6b2f6196e07abe883552cf56e we're not planning on doing a release very soon, but if you tell me the OS you use, i can make a pre-release version available for you. you'll want to place in your 0000.yaml file: minAp...

> So the fix would be to invalidate filePath when widthScale or heightScale appear in oChanges this does seem like an avenue we could pursue ... good work. > we cannot anticipate the image size from the source or options alone yeah i understand. is it possible to use a dummy model? i.e. one that con...