• 0

    posted a message on Fortress (unofficial thread)
    Oh I think I missed the little through in your text... I'll look into this.
    Posted in: Data Broker AddOns
  • 0

    posted a message on Fortress (unofficial thread)
    Quote from Saynt »

    Text justification?

    StatBlockCore has it but doesn't allow to hide all the text (show icon only).


    Good idea

    Quote from Kerecha »

    Any way to change vertical spacing and/or remove borders?

    With boprders and all theres a huge gap between 2 rows of plugins (imo its huge, want them a lot tighter together).

    Almost got all my fubar replaced properly now (thou a bunch is still only through fubar2db) but the spacing and border makes it hard to get it to look right.


    I just added a 'Show Border' setting, that let's the blocks (if disabled) stick together without any gap.
    For scalable borders or gaps I'd need terrible hacks, because those things are currently handled by the LegoBlock library. Maybe I'll remove the lib in future and create the blocks on my own.

    Quote from Astaldo »

    The 'Hide on Mouse-out' setting doesn't behave as expected when the plugin has a tooltip attached
    and you "mouse-out" through it's tooltip.

    I'm not sure my description is sufficient :)

    Imagine that you have a few plugins docked side by side at the top of the screen in a panel-like configuration.
    When you mouse-out to the left or right (toward other plugins or 'empty' screen) the plugins hide like the option says.
    When you mouse-out 'down' passing the cursor through the plugin tooltip, the plugin will not hide.

    Only tested on the current WotLK beta.

    This is working as intended. In my opinion showing the tooltip with the actual plugin hidden would be strange. The plugin should be hidden when you leave the tooltip, though.
    Posted in: Data Broker AddOns
  • 0

    posted a message on Fortress (unofficial thread)
    Quote from Darkmoone »

    For some reason it's not saving it's locked state. If i relog it will shift out of place.

    I'll look into this.

    Quote from str1k3r »

    Feature request:
    - changing block position using coordinates

    Pixel perfect positioning is not possible due to the way the interface is rendered, so this feature won't be that useful. Maybe I'll add it later, though.


    - suffix changing(Fortress blocks have suffix with all capitals letters)

    The suffix text is controlled by the DataBroker object, Fortress won't mess up with this.

    Quote from ShaneSveller »

    Feature request:
    Allow the list of blocks in Fortress to be sorted by name/addon name. Skimming through my list of scattered addons that seem to be ordered haphazardly is getting harder the more LDB addons I pick up.

    The order of the options in the options panel is the order of registration, there's no way to change it afterwards.


    Question:
    I'm going to look at the code in a few minutes but how hard would it be to work with Fortress blocks programmatically? In other words, how hard would it be to configure Fortress blocks from another addon via Lua? Say I want to adjust my oUF layout and then position certain blocks near my UFs, but I want it hard-coded. "If this block exists, put it exactly here. If this one also exists, stick it to the right-hand side of the first." and so on.

    This should be possible. The blocks themselves are named 'LegoFortressNameOfTheBrokerFeed'. The position is controlled by the LegoBlocks library, but all other things can be changed by altering the specific DB entry and calling Fortress:UpdateObject(name, [object]). The interesting parts of the code are in the Core.lua.
    Posted in: Data Broker AddOns
  • 0

    posted a message on [Idea] Rez the incoming/outgoing whisper colors
    To re-add the option to the chat config, you could use this addon. You can disable (or remove) it when you're done.
    Posted in: Addon Ideas
  • 0

    posted a message on AceGUI-3.0 TabGroup
      tabGroup.frame = mainFrame

    causes the problems. The frame member is the TabGroup's internal frame. You should not change the objects returned by AceGUI:Create directly, they all have a userdata member, that is safe to use.
    So use the following line instead.
      tabGroup.userdata.frame = mainFrame
    Posted in: Ace3
  • 0

    posted a message on Fortress + kgPanels + FuBar2Broker + FuDPS
    You don't need any other mod to run Fortress.
    Posted in: Data Broker AddOns
  • 0

    posted a message on Fortress (unofficial thread)
    Quote from Lindalas »

    I like the new treatment of global vs. local settings. One thing however is that while global settings affect all blocks (when changed), the blocks that have any "local changes" don't remember the global settings when I relog. Specifically I've set all blocks to be at 80% scale. On a few blocks I've changed what is displayed thus making them partially localized. These blocks will revert to 100% scale when I relog (but going into the global setting and moving the scale around and resetting it to 80% fixes it).


    Does this only affect the scale or also other settings? In theory it should apply the scale settings once the plugin loads and it should use the the right global or individual value...

    Edit: Found the bug and fixed it, the new version is uploaded to the SVN and should be downloadable from files.wowace.com in a few minutes. There were two saved scale values, one from Fortress and one from LegoBlock (the lib used to create the blocks). Unfortunately LegoBlock restored it's own saved scale right after the real one and so resets it to 100%. Now the modified scale is saved in both dbs.
    Fixed another bug too, new blocks weren't cascading as they should.
    Posted in: Data Broker AddOns
  • 0

    posted a message on Broker_Clock
    Quote from Funkydude »

    The true value of AceTimer comes when you have many timers. The reason why all my timers use AceTimer. It's a lot less stressful on the CPU than many OnUpdates. (Exluding places where you're updating multiple times per second)


    Ok, I didn't thought so far...
    Posted in: Data Broker AddOns
  • 0

    posted a message on Broker_Clock
    Quote from Funkydude »

    Should be fixed now, although not sure why it was changed off acetimer. I'll be making two clocks, simple and advanced both using acetimer in the near future.


    The AceTimer version was an old LDB-1.0 test plugin that got "accidentally" converted to LDB-1.1. I think for such an easy task AceTimer is too much, so it uses OnUpdate now. It's just a simple function call every 1 or 60 seconds (seconds/minutes mode).
    Posted in: Data Broker AddOns
  • 0

    posted a message on LibDataBroker-1.1 not-really-official thread
    A display could call the objects OnEnter after handling the tooltip things. But if OnEnter is only meant to handle tooltips it should be renamed to ShowTooltip, as OnEnter would be a misleading name.
    Posted in: Data Broker AddOns
  • 0

    posted a message on LibDataBroker-1.1 not-really-official thread
    Quote from tekkub »

    Why do people report shit that's ON A WIKI?

    Well, as you are the only one who ever edited something there...


    Fixed the type/tooltiptext thing. The rest is correct, feed shouldn't provide both OnEnter and tooltip, and that's stated.


    Quote from spec »

    It?s possible that a source addon may provide more that one tooltip method. The display addon should only use one of these (even if it support all three in the spec). The generally preferred order is: tooltip > OnEnter/OnLeave > OnTooltipShow.


    What if my data feed does something that has nothing to do with tooltips in OnEnter and wants to show it's text for the tooltip in OnTooltipShow? The display could provide both, but only OnEnter is called, so the tooltip is never shown... This may sound very unlikely, but as LDB is very general, this possibility should be considered.
    Posted in: Data Broker AddOns
  • 0

    posted a message on LibDataBroker-1.1 not-really-official thread
    There is some outdated information in the wiki:

    In "How to provide a dataobject":
    The example for the quicklauncher shows a LDB object with .launcher set to true, instead of .type == "launcher".
    The example for a datafeed has .tooltiptext set, but according to the spec there is no .tooltiptext anymore. Also .type == "data source" is not set (though I doubt any plugin have set this...)

    The "Addons using LDB" section is outdated. As it is hard to keep this up to date, I suggest to remove this site and just link to WoWInterface and this subforum.

    In the "Handling tooltips" section of the data spec stands display addons should not fire OnEnter/OnLeave if they found .tooltip, but I think those two methods are generic enough to be executed anyway. Maybe a plugin does other things than showing a tooltip in OnEnter (e.g. show a different text).
    Posted in: Data Broker AddOns
  • 0

    posted a message on Fortress (unofficial thread)
    Should be fixed now.
    Posted in: Data Broker AddOns
  • 0

    posted a message on Fortress (unofficial thread)
    Quote from durcyn »

    edit: okay, i see it now, toggling enable forces a disable, but the db gets overridden by the default master inheritance. maybe Enabled shouldn't be inheritable?

    Aye, I'm changing this at the moment.


    also, can you change the slash handler to call InterfaceOptionsFrame_OpenToFrame() instead of AceConfigDialog, since none of the plugin options render in the ACD frame?

    That's a good idea, I'll change that.

    Edit: Done, hopefully this is fixed now.
    Posted in: Data Broker AddOns
  • 0

    posted a message on Fortress (unofficial thread)
    The get returns 'true' because the enabled options is inherited by the master settings (without any chance to change it). I think 'enabled' should be handled individually for each plugin, I'll rework this part a bit.
    Thanks for the report, I always manage to miss something in my tests :(
    Posted in: Data Broker AddOns
  • To post a comment, please or register a new account.