Just so you don't have to keep going to the first post each time I'll post the next set of planned changes ( which could be changed if unable to be done at the time ).

1.03.00 - Implementation of the 3.3.3 Test Server changes before it goes live if possible that will either work in 3.3.2 as well or will be an in test version until it goes live.

Current changes applied and in testing:

• Multiple Anchor Option
  • This will involve only adding a single extra anchor, the compacted version. The expanded anchor will be the regular anchor used if not using the multiple anchor.
• Locked Options
  • Added Right Button for Dragging frame as I noticed it would sometimes cause the frame to move unexpectedly if you did accidently press the right mouse button.
• New: WiderWatchFrame options
  • Added ExpandedWidth value and UseExpandedWidth flag to WatchFrame with default settings. These are in place for use by people that may wish to utilise the Extra Wide Watch Frame option added in 3.3.3 but at present the addon doesn't allow you to programmatically change the width but instead automatically uses the width setting set in the slash commands or interface and will actually override the hard coded setting. If people request the option of a second width value to utilise that flag then it can be done with little problem *touches wood*.
  • New function WatchFrame_SetWidth hooked into to revert the width changes set by the default WatchFrame and use our settings instead. Seems to be working well so far and takes into account any future use we may make of the new WatchFrameWidth flag.
  • Added new event to watch for the WatchFrameWidth standard interface option change and to use the ExpandedWidth value instead of the DefaultWidth. Note that as I mentioned earlier at present these values are set to the same adjusted standard width and thus will be no difference when using the flag.
• New: Disabling of CollapseExpandButton
  • Added WatchFrameCollapseExpandButton: Disable to our disabled functions rofl. As it seems to disable at points and never re-enable again. Could be due to a bug but will see after testing further with the default settings to see how it should work.
• New:WatchFrameHeader button
  • Reparented WatchFrameHeader instead of WatchFrameTitle if it exists as this is the new watchframe header button that you can right click to get extra options.
  • Currently testing the new right click menu options to see how they work with our scroll frame. The manual moving of watched items seem to work fine. Having problems with the toggling of display of completed quests which auto collapses if there end up being no *visible* watches due to the value I test periodically being emptied without apparent reason, perhaps timing but will have to see.
• AutoHide Option
  • Currently testing how the built in autohide works in relation to our scroll frame to see if our autohide option is no longer required.

If I do any changes to these or find some more I will adjust accordingly. Once I have it working without nUI installed I will test it with nUI and then finally test both again in 3.3.2 unless 3.3.3 goes live in the mean time rofl.

__________________

Rofl I just realised what you meant here. I missed the important few words of 'for those who choose NOT to use multiple anchors' rofl. At present it ties to the topleft of the frame but I could add the option to change it. Maybe when I introduce the font stuff for 3.3.3 if I ever get the ability to get the Test Server's version to work *sigh*.

__________________

Makes sense actually. Rofl. I'll try and get that working while running those tests on Monday.

__________________

Thanks. I have some theories of what could be happening but until I see it in action I won't know for sure. I probably won't get to working on it until Monday though.

And I see where you are coming from with the anchor situation. At present switching from multiple anchors and back uses 3 different anchors so with multiple it uses ( collapsed/expanded ) and with it turned of it uses ( default ). It remembers the last default setting and will only change it once you have repositioned the frame in non multiple mode. If I change it to record convert the last expanded anchor to become the new default anchor if you turn off multiple would that be what you were expecting ?

__________________

MTRazer,
Let me know if you find anything else. I've relogged several times with it collapsed and expanded with no problems once I corrected those I came across of course

__________________

Okay, for those that have been keeping track of the bug related conversation, then you will see that I now have a solution for it. However, the nUI Docking system still has problems when you first dock to the infopanel. Doing a reloadUI or relogging will solve the problem. It looks at first as if it works but due to an error that occurs it stops the watch frame itself from updating.


-------------------------------------------------------------------
[Version 1.02.01]
-------------------------------------------------------------------

SWF_Main.lua
-->Default the Heading, Button and Watched Lines as Shown as Blizzard may have hidden already
-->Removed OnResize script and function as they were actually redundant
-->Added OnUpdate function which can be called to carry out tasks before a final call to WatchFrame_Update
-->Restore the WatchFrame Status if not in an infopanel
ScrollFrame.lua
-->Temporarily Unlock frame for resizing of subcomponents
-->Removed OnSizeChanged script. Instead resizing will be done when we want
WatchFrame.lua
-->Don't restore Watch Frame Status in case we don't want to
SWF_SlashCommands.lua
-->Only Restore non InfoPanel frames and just expand the infopanel ones

__________________

Ah Gotcha. Sounds like a reasonable idea. Maybe for the 3.3.3 version after I see what stuff they end up doing to their frame that I can either drop from mine or stop from theirs.

As to the current version. I believe I have got it back to the stage where it is doing what I expect it to do apart from the nUI glitch which I am discussing in the nUI forums to identify a better way round it. I'll finalise the code and upload it shortly. I jumped through about 6 of my characters going back and forth going from expanded to collapsed and docked and not docked and it looked to have kept it's setting and restored it correctly when it should.

The fact that I ended up removing some of the code I added last I suspect my attempts at getting the nUI docking feature incorporated messed up other stuff. Both now seem to be doing what they should ( nUI docking almost rofl ) so I am happy to post it up.

__________________

Ah, think I have got to the main brunt of the problem. If you have it locked it messes up the whole resizing including auto expanding and collapsing to reflect the last status when you next log in. The WatchFrame itself does what it is supposed to do but my own frame isn't. So I will work on that and hopefully won't take the 11hrs I spent on this yesterday rofl.

Ah, finally got the bug you got and I haven't got a clue why apart from the fact I got a WTF corruption when I got the nUI Options error causing blank frames to appear. Did that happen to you while testing or are you not a nUI user ? Just trying to tie down a common link somewhere as this is the only time I saw that problem.

Yep, looks like your title and button disappearing is caused by the same delay affecting some other stuff. In that instance the watchframe has managed to jump in and hide the heading and button ( as happens in the default watch frame ) before my code gets to the point of stopping that from happening. I fixed it by making sure those are shown before turning off the hide function.

Still undergoing testing but hopefully in the next couple of hours I should have a fixed version. My apologies that I didn't catch this in yesterdays testing and thanks for highlighting it for me.

__________________

Okay, actually tested on a new character, and I apologise for not doing that before *slaps head*. I am guessing that some values are not being set correctly as a default and its messing things up.

Anyways, I started by default with the nUI docked status which didn't show the tracked quests or heading. I thought I had fixed this yesterday but I guess not. Will look into that later.

I then undocked it and it opened up. I set the boxes to what you had and minimized the frame and logged out to desktop. I logged back in and it came back as maximized with the caption and button but no tracked quests. After confirming that I had quests still marked as tracked I then clicked the expand button despite it visually being expanded and it expanded and repositioned where it was supposed to be. So this looks like on log in, it's not setting things up right. Perhaps, as I suspect its a timing situation as I am currently running at 350ms latency so I guess the watch frame is lagging slightly. So, I may have to look into why it seems to be doing this now rather than before.

But thanks again for highlighting this problem and I will endeavour to correct it.

__________________

Hmm, thanks for that. Seems to have introduced some unusual results since incorporating the UI for the slash commands.

The reason for the multiple anchors was a decision based on if you had an interface where there was a spot you wanted it to specifically collapse to but when you expand it would expand to where you wanted to. Simply not using multiple anchors should ignore that option and it is the default setting.

I'm sure I logged out with it minimized but I will check again. However, if you have it set to autohide when nothing is being tracked and when you next log in it sees you as not tracking anything it will not show it until you track something. Autohiding is a default feature of the tracking window so I have it set as default with the option to keep the window visible even if you don't have anything being tracked. This problem you are describing could also be linked to the delay I noticed last night myself whereby initially when you log in the watchframe itself isn't available for a few seconds. Seeing as my addon uses that frame it may be causing a glitch. I'll investigate it shortly and see if I get the same effect.

The anchors themselves are auto tracked to be the top left of the frame. That way you can anchor it to the left hand side with the top left positioned where you like and if you decide to move it the right hand side the width will reflect where the top left will appear. Just dragging to where you want should be enough for it to store the new point. Turning multiple on will store the current position/state with the other state defaulting to center. IE. You had a collapsed tracker positioned in the top center and chose multiple anchors the addon will store the current top center position as the collapsed state anchor and the expanded state anchor would then be defaulted as center.

All of the settings are kept and if there are different settings between collapsed/expanded such as the anchors all 3 values will be at the last value it was since the last reset. So, to repeat :

Default Anchor : Used by default and initially center
Collapsed Anchor : Used by multiple anchor option and initially center
Expanded Anchor : Used by multiple anchor option and intiially center

Once you have moved these under whatever state the frame and anchor option are they will be used next time. If they don't it's bugged as that was the whole idea.

Hope that explains things a bit better. But I will do some more testing and confirm it is doing what it is supposed to do.

__________________