This is not reacting the way I would expect then.
I've set the code up to use strict coordinates:
Column 1 (1 card): x: 20, y:100
Column 2 (2 cards): x: 108, y:100/115
Column 3 (3 cards): x: 196, y:100/115/130
Column 4 (4 cards): x: 284, y:100/115/130/145
Column 5 (5 cards): x: 372, y:100/115/130/145/160
Column 6 (6 cards): x: 460, y:100/115/130/145/160/175
Column 7 (7 cards): x: 548, y:100/115/130/145/160/175/190
If the card is card 1, it sets the card location to 20, 100, absolutely.
For the 2nd - 7th cards, the card locations are set to xdp (20) + 88. So that they're dealt in a row, across, 88 apart (70 card width + 18 pixel space).
If the card is card 8, it sets the card location to 108, 115 absolutely.
For the 9th - 14th cards, the xdp is again incremented by 88.
If the card is card 15, it sets the card location to 196, 130 absolutely, and every card after on that row is incremented by 88.
This continues with each row being laid. The first card is set absolutely, the rest of them are spaced 88 apart on the x and located at the same y.
What I don't understand, is how the code is reacting.
As you can see, there is no space between the first and second cards of row 1. Because the first card on row 2 is perfectly aligned with that on row 1, I'm thinking it's the very first card which is not dealing in the proper location. Further, spacing between the cards does not look even. It should be 18 pixels across. In some areas it looks less.
Then, at the end of row 3, you can see how the last cards are pushed in, and then the same thing happens in a column within the last couple of rows.
Since I believe my math to be sound, I can only assume there's a logic error. However, my logic also appears to be technically correct BASED ON WHAT I KNOW.
I was concerned that loading was occurring in a different order, and that the load was causing my logic to be incorrect. However, when I placed message boxes in the VBScript and Plugin tabs, it ran the message boxes in the VBScript tab to completion, before running the one in the plugin tab. This appears to be counter to what you've said however, and to what I've observed.
I've run a whole series of tests by changing the starting xdp on frame load. And doing so is causing unpredictable results for some reason.
I'm at a complete loss, and very frustrated.
If the idx = 0 on frame load, then it shouldn't move a hotspot at all, since there's no hotspot 0, correct?
Yet, somehow, hotspot 1 is showing up at the load location, even though if the hotspot idx were 1, it should be incremented to 108. Further, if I change the xdp to 0 on frame load, which should be incremented by the hotspot click, the card loads at x:0.
A woman on a mission - a budding artist looking for a place to take root, a builder looking for the right community - I'm looking for a home.