You can call the macro with a starting number for the hotspot IDs.
You'll only need one additinal parameter. This works totally fine.
If the number of hotspots inside the macro is dynamic and you don't know how many there are in advance you can either return the final hotspot ID from the macro.
Or....
Hotspots need to be unique, from v25 on this will be especially enforced.
But they don't need to be consecutive. This means you can just "reserve" a "corridor" for the hotspots. Example code below.
! example
unID = 1
hotspot2 ... unID : unID=unID+1
...
call "macro" parameters startID = unID returned_parameters unID_ret
unID = unID_ret
!----- OR -----!
! (without ID handover and returned_parameters)
call "macro"
unID = unID + 1000
! where 1000 is a number you know won't be exceeded
However with macros which are not done by you it's quite tricky, because the way it's programmed might collide with your unique IDs.
The solution then is to start in your main GDL with a really high number for the hotspot ID.
Again: the IDs don't need to be consecutive, nor do they even need to be in ascending order.
Still the corridor/fixed offset method has one advantage:
Since the ID is used to bind the dimension to this place you won't lose important dimensions or have them re-placed randomly when changing the object.
E.g.
Hotspots •
(Macros)
Consecutive Hs IDs:
•---(•---•---•)---•---•---(•---•)
1 2 3 4 5 6 7 8
Object changed:
•---(•---•)---•---(•---)
1 2 3 4 5 [new IDs]
1 2 3 4? 5 6? 7 8? [old IDs]
Dimensions bound to ID 4 and onwards will be placed wrong!
Fixed offset:
•---(•---•---•)---•---•---(•---•)
1 10 11 12 30 31 50 51
Object changed:
•---(•---•)---•---(•---)
1 10 11 30 50 [new IDs]
No dims re-placed 🙂
