issues with PopupDetail

[Dean]

Hi Aaron
I have noticed when creating a new PopupDetailCollection I am getting
the following error opt.stickyWinToUse is not a constructor

this.stickyWin = new opt.stickyWinToUse($merge(opt.stickyWinOptions, {
relativeTo: this.observer,
showNow: false,
content: this.content,
allowMultipleByClass: true
}));
Although when I link to http://www.clientcide.com/scripts/clientside.moo.v1.2.packed.js
I get no error

I have tried clientcide-trunk-2.1.0.js and clientcide-trunk-2.0.3 and
get the same error.
Regards
Dean

[Aaron Newton]

Sounds like you are missing StickyWin. Did you use the download builder at http://clientcide.com/js ? 

[Dean]

Hi Aaron
Yes I used the download builder.
From memory I checked everything in the builder except for debug.
Im not missing StickyWin as you can see here http://www.buyaphoto.net/test2/test.html,
if you mouse over the links Popupdetails should run, if you click on
the link StickyWin runs.
Regards
Dean

[Aaron Newton]

Running the unit tester:

http://www.clientcide.com/tests/

it works. It's important to note that the unit tester loads each file in -core, -more, and -clientcide individually from source, in order. Something is missing or wrong with your built version of the library...

[Dean]

Ok Thanks Aaron
Ill have another go with the builder
Regards
Dean

[Aaron Newton]

I just fixed it. The builder was including PopupDetails before StickyWin, and this was causing issues. Download it now.

[Dean]

Thanks Aaron
Its working now.
Glad you picked that up quickly, I was swearing at myself and people
around me were starting to give me funny looks :-)

[Aaron Newton]

thanks for the heads up.

[Dean]

Hi Aaron
The change you just made seems to have affected other coding.
Just trying to figure our what and where at the moment
Regards
Dean

[Aaron Newton]

you mean adversely?

[Dean]

Yeah
I cant seem to use setPosition now http://www.buyaphoto.net/test2/test.html

[Aaron Newton]

.setPosition and .position changed places. .setPosition is the opposite of .getPosition (as it should be, now) so it takes x/y coordinates. .position is the one that lets you position an element relative to another.

in theory, both functions know how to interpret each other's arguments, so this shouldn't be a breaking change.

I really don't know why this would have broken anything given that all I changed is that PopupDetails now loads after StickyWin, neither of which touch the positioning code...

[Dean]

strange hey