Problem dynamic adding hotspots in v1.19

Hello Klaus!

I found some problem in version 1.19, with the addition of dynamic hotspots.
If hotspot count is more than 11, then the old hotspots are losing their previous indexes.
For me, sequence is an important index in the array, as it did in older versions krpano.

Unfortunately function "sortby()" does not help to completely solve the problem.
Perhaps this behavior is a problem in the new version or it is a new algorithm of the function "addhotspot()"?

Is it possible to somehow fix the problem in version 1.19?
Thank you!

<action name="test">
	txtadd(hs, 'hs', get(hotspot.count));
	addhotspot(get(hs));
	trace('FIRST: ', hotspot[0].index, ' = ', hotspot[0].name, ' || NEW: ', hotspot[get(hs)].index, ' = ', hotspot[get(hs)].name);
</action>

INFO: FIRST: 0 = hs0  || NEW: 0 = hs0
INFO: FIRST: 0 = hs0  || NEW: 1 = hs1
INFO: FIRST: 0 = hs0  || NEW: 2 = hs2
INFO: FIRST: 0 = hs0  || NEW: 3 = hs3
INFO: FIRST: 0 = hs0  || NEW: 4 = hs4
INFO: FIRST: 0 = hs0  || NEW: 5 = hs5
INFO: FIRST: 0 = hs0  || NEW: 6 = hs6
INFO: FIRST: 0 = hs0  || NEW: 7= hs7
INFO: FIRST: 0 = hs0  || NEW: 8 = hs8
INFO: FIRST: 0 = hs0  || NEW: 9 = hs9
INFO: FIRST: 0 = hs0  || NEW: 10 = hs10
INFO: FIRST: 0 = hs5  || NEW: 11 = hs11
INFO: FIRST: 0 = hs6  || NEW: 12 = hs12

Now I came up with a solution that emulates the correct index.
Yet this is just a workaround to solve the problem.

<action name="test">
	txtadd(hs, 'hs', get(hotspot.count));
	addhotspot(get(hs));
	sub(hotspot[get(hs)].order, hotspot.count, 1);
	hotspot.sortby(order);
	
	for(set(i,0), i LT hotspot.count, inc(i),
		trace(i, ' ', hotspot[get(i)].index, ' ', hotspot[get(i)].order, ' ', hotspot[get(i)].name);
	);
	trace('-------');
</action>