jamovi

hi,

yes, you'll want to use a transformed variable ... see the following screenshot




having said that ... we're very close to pushing out a fix to this issue.

jonathon

let us take a look at this ... we really want to discourage people from using the Html element as much as possible.

jonathon

hi,

this is a known issue. the maintainer of MAJOR has been missing for some time, and so far progress to address this issue has been slow going.

sorry we don't have better news.

jonathon

Ah, apologies for the misunderstanding. I have something for you that I think will work. Rather than a computed variable, use a transformed variable instead. Use the variable with the missing values as your source. You'll need to create a transform with the default formula, i.e. $source Sorry for th...

hi, can you double check that for me? it works for me. observe that the 500 no longer appears in the contingency table. you'll need to use the new column in the analysis of course. i think we have a fix for this issue in the pipeline, but i think you should be able to get this to work in the mean ti...

FYI, we did find a bug in $setSize2() ... fix will go out in 2.7.18

jonathon

hmm, i don't think there's a straightforward way to do this in jamovi ... i think we need to implement some sort of SORT() function your best bet might be to use the Rj Editor+ as follows: sorted <- apply(data, 1, sort, decreasing=TRUE, na.last=TRUE) data <- as.data.frame(t(sorted)) you'll see this ...

the virtualisation on arm64 windows machines should run the x64 version ... that's worked for me.

but yes, the cloud version is a good option too.

jonathon

we might need a screenshot of the SPSS feature you're describing.

jonathon

hi, yes, i would move your $setSize() into .init(). the general rule is to do as much in .init() as you can. you can also use $setSize2() https://dev.jamovi.org/api_image-sizing.html let me know if there are any outstanding issues after that. > How exactly does the saving process work? Does it trigg...