Combatibility issues between inq 4 and 5

Back

Home
»
Millisecond Forums
»
Inquisit 5
»
Combatibility issues between inq 4 and 5

Combatibility issues between inq 4 and 5

Author	Message
briancjo	briancjo posted 9 Years Ago Topic Details Share Topic
Group: Forum Members Posts: 25, Visits: 167	Supreme being off all kind, After finally getting all my damn code set in inquisit 4, I'm having compatibility issues on inquisit 5 and the web player. Any scripts both created by me and standard premade scripts (ipanant) that have htm instructions are not running properly; it shows blank screens that does not forward. I thought it was initially a mac and. PC problem but having recoded an htm instructions to trial/picture script that worked on a PC using inquisit 4, even that does not run on the web player or inquisit 5. I thiught Inquisit 5 was backwards compatible but am I missing something?
	Reply Like 73
seandr	seandr posted 9 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 1.3K, Visits: 5.6K	Inquisit 5 is indeed backward compatible with 4. From your description, it sounds like something else might be going wrong. Is it possible to attach your script? Or send a link to the launch page if you are running it online? Thanks, Sean
	Reply Like 66
Dave	Dave posted 9 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 13K, Visits: 105K	+x briancjo - Saturday, November 19, 2016 Supreme being off all kind, After finally getting all my damn code set in inquisit 4, I'm having compatibility issues on inquisit 5 and the web player. Any scripts both created by me and standard premade scripts (ipanant) that have htm instructions are not running properly; it shows blank screens that does not forward. I thought it was initially a mac and. PC problem but having recoded an htm instructions to trial/picture script that worked on a PC using inquisit 4, even that does not run on the web player or inquisit 5. I thiught Inquisit 5 was backwards compatible but am I missing something? Could you post the respective script's <instruct> elements here? Particularly, their /windowsize attributes. There may be a few cases where Inquisit 5 interprets the values given there differently than Inquisit 4. For example, <instruct> / windowsize = (800, 600) ... </instruct> would by default be interpreted as percentages, i.e. the instruction pages would be much "larger" than the visible screen area, leading to the impression of a "white screen". The fail-safe option is to always specify the unit. I.e., if you want the pages cover 80% of the display area's width and 90% of its height, specify <instruct> / windowsize = (80%, 90%) ... </instruct> Similarly, for an area of 800 by 600 pixels, /windowsize would read <instruct> / windowsize = (800px, 600px) ... </instruct> Hope this helps.
	Reply Like 68
briancjo	briancjo posted 9 Years Ago ANSWER Post Details Share Post
Group: Forum Members Posts: 25, Visits: 167	+x Dave - Sunday, November 20, 2016 +x briancjo - Saturday, November 19, 2016 Supreme being off all kind, After finally getting all my damn code set in inquisit 4, I'm having compatibility issues on inquisit 5 and the web player. Any scripts both created by me and standard premade scripts (ipanant) that have htm instructions are not running properly; it shows blank screens that does not forward. I thought it was initially a mac and. PC problem but having recoded an htm instructions to trial/picture script that worked on a PC using inquisit 4, even that does not run on the web player or inquisit 5. I thiught Inquisit 5 was backwards compatible but am I missing something? Could you post the respective script's <instruct> elements here? Particularly, their /windowsize attributes. There may be a few cases where Inquisit 5 interprets the values given there differently than Inquisit 4. For example, <instruct> / windowsize = (800, 600) ... </instruct> would by default be interpreted as percentages, i.e. the instruction pages would be much "larger" than the visible screen area, leading to the impression of a "white screen". The fail-safe option is to always specify the unit. I.e., if you want the pages cover 80% of the display area's width and 90% of its height, specify <instruct> / windowsize = (80%, 90%) ... </instruct> Similarly, for an area of 800 by 600 pixels, /windowsize would read <instruct> / windowsize = (800px, 600px) ... </instruct> Hope this helps. DAAAAAAAAAAAAAAAAAAAAAAVE, seriously I was on the verge of quitting, and you, like the DIVINE BEING YOU ARE, just brought me back to life. My name is now Lazarus! THAT was really annoying about the window size. I'm sure that was somewhere in the documentation, but that should be the first thing ever said for those going from Inquisit 4 to 5, especially since some of the scripts were written for Inquisit 4 like the IPANAT, and people using it would have no idea why scripts were not running correctly with the transition to the Inquisit 5 web player. SERIOUSLY Dave, you are psychologically testing programming divinity in my book. Where do I add the gratuity!?!
	Reply Like 60