Once again, i greatly appreciate the advice and wise counsel. These posts are of great value to me as I get deeper into LimeSurvey and learn the specifics.
In this case, I see the .array-flexible-column class as the target element rather than my solution which relied on having just one question per page where I knew [id^=question] would work. Your solution appears to be more relevant.
The primary thought behind custom.js as a resource is establishing an architecture I can use for any survey. I often use this approach with stylesheets, e.g., custom.css, so i can quickly isolate styles I've added that override the base theme/template. I hear your recommendation and for the time being, I'll keep everything in template.js as I learn more.
Thanks again for taking time to review this post.
In this case, I see the .array-flexible-column class as the target element rather than my solution which relied on having just one question per page where I knew [id^=question] would work. Your solution appears to be more relevant.
The primary thought behind custom.js as a resource is establishing an architecture I can use for any survey. I often use this approach with stylesheets, e.g., custom.css, so i can quickly isolate styles I've added that override the base theme/template. I hear your recommendation and for the time being, I'll keep everything in template.js as I learn more.
Thanks again for taking time to review this post.