(183Kb)

Updated: 12-20-20 05:30 PM

Add Favorite

Install Help

Pictures

File Info

Compatibility:	Shadowlands patch (9.0.2) Shadowlands pre-patch (9.0.1)
Updated:	12-20-20 05:30 PM
Created:	12-03-08 07:08 PM
Downloads:	92,091
Favorites:	754
MD5:

DockingStation (Display)

Version: 0.5.26 (Beta)

by: Vrul [More]

A display platform for LibDataBroker (LDB) based plug-ins. The display is provided through panels, each having sections (Left, Center, Right) corresponding with how a plugin is justified within it.

All plugins are disabled by default and you must turn on the ones you want to use. This is to avoid the complete mess that results from all plugins being on with the first use. The only plugin on at the start is the one provided by this addon to access its options easily. Just click it to start changing settings.

With plugins unlocked you can drag and drop them to other panels/sections and have them automatically adjust to their new location. There are no limitations on the drag and drop capabilities other than the new location for a plugin must be within a panel. You may also change the location of a plugin through the plugin options menu.

Almost all sub-sections of settings have a default option. The defaults follow a set pattern. First plugins check their settings, if default, they next go to their panel's settings. If the panel is also set to default then it defers to the addon's global settings. Finally, if the global settings are still set to default, then the hard coded defaults are used.

Note: It is recommended that you delete the folder(s) for an existing addon when updating to a different version. This is to keep files that are no longer used from taking up space.

Translators: To submit a translation please just edit existing files (example: DockingStation\Locales\deDE.lua and DockingStation_Config\Locales\deDE.lua) and send them to me.

Version 0.5.26 (12/20/2020)
- Changed way position is calculated

Version 0.5.25 (10/16/2020)
- Bug fix for SetBackdrop error with recycled panels

Version 0.5.24 (10/16/2020)
- Fix for not being able to see background option changes

Version 0.5.23 (10/16/2020)
- Retail fix for previous class update (actually tested changes on retail and classic this time)

Version 0.5.22 (10/15/2020)
- Minor tweak to remove an error with WoW Classic

Version 0.5.21 (10/14/2020)
- Updated for 9.0

Version 0.5.20 (01/14/2020)
- Changed reference of InterfaceOptionsFrameHeaderText to InterfaceOptionsFrame.Header.Text

Version 0.5.19 (10/25/2019)
- Fix for NamePlateTooltip error

Version 0.5.18 (09/01/2019)
- Minor edit to Jostle.lua to not generate an error on WoW Classic

Version 0.5.17 (08/12/2019)
- Removed a minor tweak to WorldMapFrame.BlackoutFrame that was causing an error with the new anchoring rules

Version 0.5.16 (09/15/2018)
- Corrected panels being on top of the world map when its maximized

Version 0.5.15 (07/21/2018)
- Removed backwards compatibility code
- Library update

Version 0.5.14 (06/11/2018)
- Added the option to rotate a plugin's icon
- Plugin icons now rotate based on the LDB field "iconRotation" (in radians)

Version 0.5.13 (06/09/2018)
- Updated for 8.0
- No longer using LibJostle, now using a more simple solution
- Combined the panel option categories "Position" and "Size" into "Layout"
- Renamed the panel option "Move Blizzard Frames" to "Shift UI"

Version 0.5.12 (08/30/2017)
- Fix for PlaySound change in 7.3

Version 0.5.11 (05/05/2017)
- Added panel options "Alpha, Fade In" and "Alpha, Fade Out"

Version 0.5.10 (04/27/2017)
- Fix for texture paths that are numbers and not strings

Version 0.5.9 (01/07/2017)
- Corrected a potential issue when updating panel/plugin widths

Version 0.5.8 (08/07/2016)
- Fix for an error when hiding UIParent with a plugin tooltip showing
- Corrected a scaling issue with LibQTip tooltip borders

Version 0.5.7 (07/23/2016)
- Library update

Version 0.5.6 (05/14/2016)
- Resolved a Legion compatibility issue

Version 0.5.5 (10/14/2014)
- Updated for 6.0
- Took another stab at eliminating the reported panel moving issue

Version 0.5.4 (08/22/2014)
- Stop causing a tooltip flashing issue for other addons

Version 0.5.3 (08/14/2014)
- Taking another shot at correcting the issue with panels not staying put

Version 0.5.2 (07/17/2014)
- Correct an issue with panels not staying where they should

Version 0.5.1 (06/07/2014)
- Fix for an error that was occurring when upgrading a version older than 0.4 and with new installations

Version 0.5 (05/24/2014)
- Library update

Version 0.4.15 Beta (09/27/2012)
- Library update to fix a potential error

Version 0.4.14 Beta (09/11/2012)
- Fix for some undesired interactive tooltip behavior

Version 0.4.13 Beta (09/02/2012)
- Updated for MoP

Version 0.4.12 Beta (07/06/2012)
- Updated for MoP Beta

Version 0.4.11 Beta (01/31/2012)
- Traditional Chinese localization 繁體中文化 by andy52005

Version 0.4.10 Beta (12/22/2011)
- Make sure all tooltips are clamped to screen

Version 0.4.9 Beta (12/21/2011)
- Fix for GameTooltip type tooltips

Version 0.4.8 Beta (12/19/2011)
- Attempt at allowing plugins that create tooltips via OnEnter/OnLeave to be scaled and reanchored

Version 0.4.7 Beta (11/27/2010)
- Fix for error when enabling/disabling an unloaded plugin

Version 0.4.6 Beta (10/13/2010)
- Libraries updated

Version 0.4.5 Beta (09/11/2010)
- Added the option to override a plugin provided label with it's name

Version 0.4.4 Beta (07/19/2010)
- Corrected a potential issue with generating panel keys
- Updated to use the new AceGUI-3.0-SharedMediaWidgets
- Minor code tweaks

Version 0.4.3 Beta (06/10/2010)
- Fix for panel positioning bug

Version 0.4.2 Beta (06/10/2010)
- Added localization support
- Corrected an issue with ConfigMode support
- Modified the behavior of the icon zoom option
- Convert.lua may now be deleted (only needs to run once each update)

Version 0.4.1 Beta (06/02/2010)
- Fixed issue with icon updates (iconCoords, iconR, iconG, iconB)

Version 0.4 Beta (05/31/2010)
- Major overhaul

Version 0.3.3 Beta (12/11/2009)
- Added MMOUI Minion support to TOC file (X-WoWI-ID)
- Library update (fixes buff frame not moving with other Blizzard frames)

Version 0.3.2 Beta (05/24/2009)
- Corrected an issue with plugins that define their type after their data object is first created
- Fixed a bug with the report option not properly hiding errors/warnings when disabled

Version 0.3.1 Beta (05/23/2009)
- The configuration window now remains centered when the panel/plugin lists are added on the side, this can be disabled with the option DockingStation-General-Center Configuration

Version 0.3 Beta (05/23/2009)
- LDB type is no longer defaulted to 'data source' if none given
- Most duplicate errors/warnings are now ignored
- Changed the way panel labels are templated
- Reworked how panels and plugins are selected in the options panel

Version 0.2.26 Beta (05/08/2009)
- Fixed a bug with panel visibility
- Updated libraries

Version 0.2.25 Beta (05/08/2009)
- Fixed a bug with panel visibility
- Changed the minimum values for panel height and width (from fixed to 1/64 of screen height and width)
- Changed the maximum value for panel height (from fixed to 1/16 of screen height)
- The options for panel height and width (Appearance) now update all min/max values instead of just max panel width on a resolution change

Version 0.2.24 Beta (04/28/2009)
- Corrected some issues with changing profiles
- Fixed an error with opening the configuration panel
- Changed the OnClick handler to better deal with other LDB displays
- Added an option to allow right clicking on a panel to open it's configuration
- Warnings are no longer generated for unsupported LDB types
- Warnings are now generated for any 'launcher' using 'data source' specific fields: text, value, suffix
- Panel tooltips are now only shown while one of DockingStation's configuration panels is open

Version 0.2.23 Beta (04/24/2009)
- More tooltip corrections

Version 0.2.22 Beta (04/23/2009)
- Taking a shot at the vanishing tooltip issue

Version 0.2.21 Beta (04/23/2009)
- Added more options for panel backgrounds

Version 0.2.20 Beta (04/21/2009)
- Fixed an issue with some string settings

Version 0.2.19 Beta (04/20/2009)
- Better support for shared media
- Trying out a new library for easier LoD options

Version 0.2.18 Beta (04/18/2009)
- Corrected an issue with panels anchored outside the screen's bounds

Version 0.2.17 Beta (04/16/2009)
- Fix for panels moving from their positions on a reload

Version 0.2.16 Beta (04/16/2009)
- Changed tooltip hiding options slightly
- Tooltip scaling is now off by default
- Enabling the report option now also provides error information for previously hidden execution problems

Version 0.2.15 Beta (04/13/2009)
- Added an option for disabling tooltip scaling
- OnMouseWheel support enabled

Version 0.2.14 Beta (04/12/2009)
- More tooltip fixes

Version 0.2.13 Beta (04/09/2009)
- Fix for plugins that call their own OnEnter function internally

Version 0.2.12 Beta (04/09/2009)
- Added panel fading
- More tooltip fixes

Version 0.2.11 Beta (03/26/2009)
- Corrected a bug with tooltip settings that are set to default
- Fixed some issues with tooltip scaling

Version 0.2.10 Beta (03/19/2009)
- Corrected a display issue with panel labels
- Fixed a bug with plugins appearing behind their panel
- Deleting a panel that contains plugins should no longer generate errors
- Fixed an issue with tooltip behavior (still not completely fixed though)

Version 0.2.9 Beta (03/18/2009)
- Changed panel labels to only show up if the Panels or Plugins configuration screen is open
- Configuration options are now visible in the Blizzard options panel for addons before being loaded
- Corrected some tooltip behavior (still not completely fixed yet)

Version 0.2.8 Beta (03/15/2009)
- Fixed a tooltip bug

Version 0.2.7 Beta (03/14/2009)
- Changed how and when setting inheritance takes place
- Added and changed tooltip options
- Revamped the way panels and plugins are locked

Version 0.2.6 Beta (03/13/2009)
- Fixed another bug with converting old settings to the new launcher name
- Changed the way panel labels are handled (old settings are no good)
- Corrected an issue when enabling plugins or changing their location via the configuration settings

Version 0.2.5 Beta (03/11/2009)
- Fixed a bug with converting old settings to the new launcher name
- Added the ability to change panel labels for easier identification
- Changed creating a panel to automatically select the settings for the new panel

Version 0.2.4 Beta (03/10/2009)
- Renamed the launcher to DockingStation_Config to avoid issues with LoD and other LDB displays that add plugin options directly to Blizzard's option panel
- Moved AceDBOptions-3.0.lua to DockingStation_Config to make it LoD
- Added the ability to edit/remove settings of plugins that are not loaded

Version 0.2.3 Beta (01/28/2009)
- Corrected an issue with plugins not inheriting their panel's settings properly upon creation

Version 0.2.2 Beta (01/22/2009)
- Fixed a bug with settings when creating a new panel

Version 0.2.1 Beta (01/21/2009)
- Changed the way plugins are updated in a panel
- Fixed a bug with the center section of panels not always staying centered
- Reverted some changes dealing with plugin strings while tracking down a bug

Version 0.2 Beta (01/20/2009)
- Reworked some high CPU usage code to require much less processing
- Added options to disable showing tooltips in combat and to allow for a small portion of panels to be moved off-screen

Version 0.1.2 Beta (01/19/2009)
- Changed the minimum value allowed for Panel Background Inset from 0 to -1 to help with the "gap" problem

Version 0.1.1 Beta (01/14/2009)
- Added a slash command (/dockingstation) that opens the configuration panel
- Corrected bugs with panel anchoring and ordering
- Load on demand for configuration is now functioning properly

Version 0.1 Beta (01/12/2009)
- Configuration is now load on demand and some options were added/changed
- DockingStation's launcher is now a true LDB plugin instead of only being available to itself
- Panels are now at different levels based on the most recently moved (persistant)

Version 0.0.25 Beta (12/23/2008)
- Fixed some bugs with options and their defaults

Version 0.0.24 Beta (12/19/2008)
- Added options for placing borders on panels
- Added support to get panel frame references
- Updated to the lastest plugin spec: iconCoords (4 or 8), iconB, iconG, iconR

Version 0.0.23 Beta (12/18/2008)
- Added an option to apply an outline or shadow to the various text elements

Version 0.0.22 Beta (12/17/2008)
- Added code to correct a LibDataBroker bug
- Fix for an issue with OnClick handlers

Version 0.0.21 Beta (12/12/2008)
- Fixed an issue with dragging and dropping plugins into the "Right" section of a panel
- Fixed an error with tooltips for some plugins
- Removed most restrictions placed on plugins

Version 0.0.20 Beta (12/11/2008)
- Fixed a bug with zeroes being removed from either ends of strings
- Fixed an error where a plugin in the process of being moved would jump back into place if it or another addon in the same panel/section was updated
- Added a new option to show warnings/errors generated during the creation of new plugins

Version 0.0.19 Beta (12/10/2008)
- Uncommented the code that broke the UI scale fix from 0.0.17 (Oops)

Version 0.0.18 Beta (12/10/2008)
- Fixed a bug with panels not always deleting properly
- The plugin type 'data source' now accepts either the field text or value, instead of just text, for initial type verification

Version 0.0.17 Beta (12/09/2008)
- Fixed a bug when utilizing the UI scale video setting
- Ability to set default settings for panel plugins and panels and plugins in general
- Can now turn off the icon for 'launchers' if the label is still showing

Version 0.0.16 Beta (12/08/2008)
- Fixed a bug with plugin label/suffix using the option "Same as Text"
- Changed the disply of panel options
- Added the option to change the panel background texture
- Plugins now listed by label (name also shown once selected if different from label)

Version 0.0.15 Beta (12/07/2008)
- Changed the way plugin options are displayed

Version 0.0.14 Beta (12/05/2008)
- More options for plugins added

Version 0.0.13 Beta (12/03/2008)
- Initial public beta release

Optional Files (0)

Comment Options

Page 24 of 43

« First

Last »

05-26-09, 08:03 AM

siema_co

A Deviate Faerie Dragon

Forum posts: 12

File comments: 64

Uploads: 7

Originally posted by Tristanian
You are wrong about this. Other display authors care just as much. While I personally agree 100% that every single plugin should ideally specify a .type attribute, I cannot see myself ever trying to enforce such a thing. Not because I don't want to or because it's hard or anything, but because I know for a fact that if I try to do so, the following things will happen :

a) 90% of the users will tell me to go **** myself and they won't edit their plugin files and to be perfectly honest, they will be right. It's not their job to do so.
b) 95-99% of the authors I will try to "bother" adding a type, will answer in a similar manner (or even worse not at all), since their plugin works fine with display X.

It's an uphill battle and the only real viable solution, is to either make "enforcing" optional, or instead of filtering out data objects by types that your display supports, I've personally elected to do the opposite. Filter out data objects that I do NOT support, since it is much more likely that specialized feeds that aren't used as "launchers" or "data sources", will at least have some unique way to separate them from the rest and usually that points to a unique .type.

You are right, but look at how many displays are there. 6, 7?
If their working display X disappeared they would have to add that f***ing ONE SHORT line of code.
I personally can't understand such ppl, what's the problem with adding one ridiculously simple line of code?
BTW thanks to DS "enforcement" i even fixed my crappy plugins lengthening the code by whole 5% XD

05-26-09, 07:53 AM

Tristanian

Andúril

Forum posts: 279

File comments: 262

Uploads: 3

Originally posted by siema_co
Maybe it would work if author of every display addon cared.
So far it's only Vrul (DockingStation) and Astromech (Carousel) which "enforce" correctly written plugins.
And it's easier to contact 5-6 display addon authors (which would also make plugin authors fix their work) than xxx plugins authors who have no real reason to correct their addons.

You are wrong about this. Other display authors care just as much. While I personally agree 100% that every single plugin should ideally specify a .type attribute, I cannot see myself ever trying to enforce such a thing. Not because I don't want to or because it's hard or anything, but because I know for a fact that if I try to do so, the following things will happen :

a) 90% of the users will tell me to go **** myself and they won't edit their plugin files and to be perfectly honest, they will be right. It's not their job to do so.
b) 95-99% of the authors I will try to "bother" adding a type, will answer in a similar manner (or even worse not at all), since their plugin works fine with display X.

It's an uphill battle and the only real viable solution, is to either make "enforcing" optional, or instead of filtering out data objects by types that your display supports, I've personally elected to do the opposite. Filter out data objects that I do NOT support, since it is much more likely that specialized feeds that aren't used as "launchers" or "data sources", will at least have some unique way to separate them from the rest and usually that points to a unique .type.

__________________

05-26-09, 03:53 AM

X-buZZ

A Kobold Labourer

Forum posts: 1

File comments: 56

Uploads: 0

Hi Vrul,

can you please give an answer to my post from the wowace forums:

Would it be possible to overide the labels of LDB plugins with own values?

Some broker addons have ugly labels so i would love to be able to override them with my own values.

Keep up the great work!

Kind regards
X-buZZ

05-26-09, 12:08 AM

siema_co

A Deviate Faerie Dragon

Forum posts: 12

File comments: 64

Uploads: 7

Originally posted by TGulics
I agree.

I'm sure there's an old adage somewhere... like "don't fix what isn't broken."

I appreciate the heck out of DockingStation and the author for making it, but in this case the simple solution is to A) either continue with what was working before or B) make a provision for both ways to work (i.e. both 'correctly written' plugins and 'incorrectly written' plugins will work). Otherwise, you put your users in a position where they're hoping the other plugin authors will change/fix their code, and many authors may not bother to do so based on Dockingstation's change... now, or ever.

Maybe it would work if author of every display addon cared.
So far it's only Vrul (DockingStation) and Astromech (Carousel) which "enforce" correctly written plugins.
And it's easier to contact 5-6 display addon authors (which would also make plugin authors fix their work) than xxx plugins authors who have no real reason to correct their addons.

Last edited by siema_co : 05-26-09 at 12:09 AM.

05-25-09, 10:18 PM

Vrul

A Scalebane Royal Guard

Forum posts: 404

File comments: 322

Uploads: 33

Re: Reverting to Previous DS

Originally posted by doktorstick
IMO, you support both, show which ones are "invalid" in your UI, and claim that in version X, you'll no longer support the broken format (but X is sufficiently far out to get mod authors to 1) learn about the problem; and 2) fix the problem).

I posted this in regards to the type field on 12 Dec 2008:

Since LDB is a generic library that can be used for much more than plugins, not enforcing things may come back to bite me in the ass. If/when that happens I'll probably enforce the 'type' field and no longer allow for defaulting to a type if not defined. It will then be up to anyone using a plugin that still isn't declaring a type to bug the author to get their **** together.

05-25-09, 09:24 PM
doktorstick A Defias Bandit Forum posts: 2 File comments: 51 Uploads: 2	Reverting to Previous DS I agree with the sentiment of the other users. I've reverted my DS to an earlier version so I can have what worked (seemingly) flawless. IMO, you support both, show which ones are "invalid" in your UI, and claim that in version X, you'll no longer support the broken format (but X is sufficiently far out to get mod authors to 1) learn about the problem; and 2) fix the problem).

05-25-09, 06:59 AM

TGulics

A Murloc Raider

Forum posts: 4

File comments: 79

Uploads: 0

Originally posted by Jexx
I agree with several others here, I'm not going to manually edit a bunch of my addons that worked perfectly before this latest version of Docking Station. I'll revert back to 2.26 until the author makes Docking Station display the plugins like it used too.

I agree.

I'm sure there's an old adage somewhere... like "don't fix what isn't broken."

I appreciate the heck out of DockingStation and the author for making it, but in this case the simple solution is to A) either continue with what was working before or B) make a provision for both ways to work (i.e. both 'correctly written' plugins and 'incorrectly written' plugins will work). Otherwise, you put your users in a position where they're hoping the other plugin authors will change/fix their code, and many authors may not bother to do so based on Dockingstation's change... now, or ever.

05-24-09, 12:36 PM
Jexx A Deviate Faerie Dragon Forum posts: 10 File comments: 118 Uploads: 0	I agree with several others here, I'm not going to manually edit a bunch of my addons that worked perfectly before this latest version of Docking Station. I'll revert back to 2.26 until the author makes Docking Station display the plugins like it used too.

05-24-09, 10:42 AM
xtoq An Aku'mai Servant Forum posts: 32 File comments: 642 Uploads: 4	The reason that it "breaks" these plugins is that they aren't written correctly. Previously, DockingStation ignored the fact they were incorrect and assumed that if there was no type they were data objects, but to be more compatible with everything else, Vrul decided to do the right thing (as coding goes) and make his code correct. You should contact the authors of your plugins that don't work and tell them that they need to specify a type in their LDB plugin. Most will be of type "data object." If you want to do it manually, you'll have to open the lua files of the plugins that don't work, and find where they have declared their LDB options (usually has some code like "icon = //Interface/Addons/Directory/icon.ext" near it) and add this to the beginning: type = 'data source', Usually, the code will look similar to this (with different text of course) Repair = { type = 'data source', icon = "Interface\\Icons\\Trade_BlackSmithing", label = L["Dur"], text = "100%", } Don't forget to back up your files first! Also Vrul, could there instead be some sort of option to have this happen? Like "ignore plugins that have no type set" that could default to off? I think this would be the best option, if its even possible. Last edited by xtoq : 05-24-09 at 10:45 AM.

05-24-09, 09:37 AM

Gsusnme

A Wyrmkin Dreamwalker

Forum posts: 55

File comments: 199

Uploads: 1

Originally posted by Normi01
Reverting back to 0.26!
Sorry but more than half of my addons dont show up anymore
and i am not going to change tons of lua files myself.
So long Normi.

I too am experiencing issues with some of my Broker add-on's no longer working (DockingStation grays them out as it does when an add-on is ENABLED in DockingStation but either has been deleted off the disk or disabled in the add-on toggle menu.)

I however am going to graciously thank you for all your hard work and dedication to this great LDB display add-on. Bugs are all in the namesake of progress!

Can someone perhaps instruct me on how to edit my other add-on's so they'll still be compatible? Thanks!

05-24-09, 09:35 AM
jdhas A Defias Bandit Forum posts: 3 File comments: 11 Uploads: 0	BasicBrokers I love DockingStation, but the latest update 'breaks' (for lack of a better term) BasicBrokers (http://wowinterface.com/downloads/in...icBrokers.html). At first all BasicBrokers plugins appeared as grey in DS. Then, after deleting the settings for all of the BasicBrokers plugins in DS and restarting (and re-installing BasicBrokers), none of the BasicBrokers plugins appear in DS (though they appear just fine in any other LDB display addon I load [i.e. Fortress, ButtonBin, etc.]). I'm happy tweaking the BasicBrokers lua to make then compatible with DockingStation. Thanks for a great addon.

05-24-09, 05:16 AM
Normi01 A Kobold Labourer Forum posts: 0 File comments: 18 Uploads: 0	Reverting back to 0.26! Sorry but more than half of my addons dont show up anymore and i am not going to change tons of lua files myself. So long Normi.

05-23-09, 05:07 PM

Vrul

A Scalebane Royal Guard

Forum posts: 404

File comments: 322

Uploads: 33

Originally posted by Skylinee
Could you disable that startup spam please? Or atleast add an option for it.

Oops, I left the check for the option commented out. Go to line 229 in DataObject.lua and remove the two dashes "--" in front of this line:

--if not settings.report then return end

That will fix it back to normal until I upload a new version.

05-23-09, 05:00 PM

xtoq

An Aku'mai Servant

Forum posts: 32

File comments: 642

Uploads: 4

Originally posted by Vrul
That is basically what I'm working towards. I'll add two new types, one of which will be 'group'. All that will do is give a way to indicate which plugins should always be moved together and/or relative to each other. It will also allow me to give options for the spacing between those plugins without effecting the spacing of plugins not in the group.

That was why I redid how the plugins are shown in the options. A group will show up like a plugin and then all the plugins that belong to that group will show up as sub-entries under it. So you can hide the group and such and have that apply to all its members.

Sweet! I was actually wanting "groups" for the longest time, but figured I was a minority so I put it on the back burner. Its especially a great idea for those like me who are a little ADD and change things around all the time. Thanks a lot and keep up the good work! Looking forward to these features.

05-23-09, 04:25 PM
Skylinee A Murloc Raider Forum posts: 5 File comments: 371 Uploads: 0	Could you disable that startup spam please? Or atleast add an option for it.

Page 24 of 43

« First

Last »

Report this File

Category Jump: