Bring Back Legacy | Voters

Bring Back Legacy

Amaranth Weasel

It’s a lot easier to code using legacy coding. Even a beginner will know what to do but using R coding is confusing. I have used Q for a lot of years and still found it confusing to code using R.

I guess ease of use should be given a priority

Created by Justin Tysoe

December 5, 2023

Jamie Morris

Merged in a post:

Bring back Legacy Coding

Dramatic Swift

Is it possible to have an option to revert to the legacy code frame, and not use the new R based code frame interface?

December 13, 2023

Justin Lew

Merged in a post:

Bring Back Legacy Coding

Dramatic Swift

Is it possible to have an option to revert to the legacy code frame, and not use the new R based code frame interface?

November 16, 2023

Justin Lew

Merged in a post:

Add legacy coding back to Q after 5.16

Quiet Alpaca

Legacy coding is still a lot quicker when working on large files but this feature has now been removed from Q 5.16.

November 16, 2023

Justin Lew

Merged in a post:

Bring back legacy coding

Dramatic Swift

Legacy coding has been removed from Q 5.16 onwards but is quicker than the current version, so this can cause issues with larger files.

November 16, 2023

Justin Lew

Merged in a post:

Add Back option for Legacy coding

Orchid Bird

We have recently updated to the latest version of Q but have now realised that one of the features that we were using has disappeared.

We have been using Q to code our open enders and have been the Legacy version Code Text feature which we really like and know how to use. We have never used the R version. In the latest update the legacy option has disappeared. Is it possible to get it back please?

November 16, 2023