[Bug] Interaction menu: Argument out of range and order of icons

ReimG

In settings I changed "Interaction method" to "Choose hotspot then interaction". If hotspot doesn't have any interactions defined (including default) the interaction menu still opens and after pressing "InteractionA" key it throws an exception "Argument out of range".

Also a minor drawback is that the navigation order in interaction menu is based on order of use interactions specified in hotspot but elements order in menu is based on icon ID. It is inconsistent in my opinion and should be changed to either one of them.

ChrisIceBox

Thank you for the bug report.  However, please state the version of AC you're using.  If not the latest (v1.52a), please update and post the new error message as the line numbers will be different.

The ordering of icons in the Interaction Menu are based on the ordering of the elements - you can re-order them in the Menu Manager without modifying either the Hotspot or the Cursor Manager.

ChrisIceBox

Please make sure you are using v1.52a before reporting console errors, as the line numbers are inconsistent otherwise.

The ordering of icons in the Interaction Menu are based on the ordering of the elements - you can re-order them in the Menu Manager without modifying either the Hotspot or the Cursor Manager.

ReimG

Thank you for quick answer. Sorry about that. I will update to 1.52a when I will have more time and post again if the error occurs.

About the ordering, more of a problem is not the order of icons (I didn't know that it is set in menu, thanks ), but order of cycling through them. When I have interactions set as shown on screenshots above then first highlighted icon is the first one next the third one and last the second one. It should always be first then second then third. For better understanding I made a gif to show what's wrong in my opinion.

http://i.imgur.com/P6GXPcg.mp4

ReimG

I updated to 1.52a, but error still occurs. Here's a screenshot:

ChrisIceBox

The ordering is based on the Hotspot's interactions, as this allows for things like the enabling/disabling of individual interactions at runtime.  I hope it isn't too much of an issue for you.

Thank you for the new screenshot - with the new line numbers I will be able to look into it.

ReimG

No problem. Just that it is not intuitive, but it is not a major problem and I just have to remember the order to avoid this problem, so it is not so bad . Thanks