CFM: Blizz frame conflict

[Sythalin]

Well, seeing as how the community over at WoW is as helpful as ever (read: COMPLETELY USELESS), I copy/paste here.

I'm having an conflict that I can't resolve with CFM.

Situation:
1) Open character frame
2) Add CharacterFrame
3) Change scale to .8
4) Change X/Y to 0
5) Close everything (ESC)
6) Open character frame

The frame sets back to it's original position, but retains scale info.

7) /reload
8) Open character frame
9) All settings apply as they should

Things to consider:
1) As soon as a frame is added to CFM, it automatically sets SetUserPlaced(true) and SetMovable(true)
2) After reload, the saved vars show that all info is being stored correctly, in both CFM's database and in layout-local.lua

It appears as WoW won't adjust the set x/y until after the reload, after which it's works perfectly from then on out. I'm trying to avoid this need of a reload if at all possible.

[Torhal]

Unfortunately, SetUserPlaced() is only effective after being written to file, which entails logging out, exiting WoW, or reloading the UI.

You could possibly set position variables in a file-local table when setting the coords, and hook the frame's OnShow script to refer to them for manually placing the frame until the next time the game is loaded - at which point the frame's coords wouldn't exist in the table and would simply be placed via the saved values.

[Sythalin]

Originally Posted by Torhal Unfortunately, SetUserPlaced() is only effective after being written to file, which entails logging out, exiting WoW, or reloading the UI. You could possibly set position variables in a file-local table when setting the coords, and hook the frame's OnShow script to refer to them for manually placing the frame until the next time the game is loaded - at which point the frame's coords wouldn't exist in the table and would simply be placed via the saved values.

Actually, I've already hooked OnShow for the frames. But now that you've pointed it out, I just realized that I made the hooks after reloads/relogs, but never placed hooks when a frame is initally added, which would most likely solve this issue. Testing now....

EDIT: Yep, that solved it. Can't believe I didn't notice it before.... >.<

[Torhal]

Originally Posted by ChaosInc EDIT: Yep, that solved it. Can't believe I didn't notice it before.... >.<

...forest for the trees...?

[Sythalin]

Originally Posted by Torhal ...forest for the trees...?

And said forest keeps getting deeper and deeper as I keep adding more trees I wasn't expecting.

[Torhal]

Aye - it's good to stroll out for a bit before you find yourself blinking rapidly, pointing at nothing in particular, and drooling from one side of your mouth whilst scratching your head.