If the bin is larger than the contents (i.e it has a fix width set), it should be fine to move them anywhere on the bin. If not, you need to move it on top of an existing button which for an empty bin is just the actual bin icon.
Some kind of visual feedback would help with this.
I'll investiage the possibility of making secure buttons work in ButtonBin (most likely on a per-bin level). The drawbacks of course is that things can't be moved or resized during combat which would require some tweaking.
I'll investiage the possibility of making secure buttons work in ButtonBin (most likely on a per-bin level). The drawbacks of course is that things can't be moved or resized during combat which would require some tweaking.
Secure stuff would need some communications between the plugin and the display. Using fields on the data object would be the perfect place:
- a "secure" or "secureTemplate" field, supplied by the plugin to provide the template(s) string, used by the display as the 4th argument of CreateFrame. That way, only plugins that provide a template field would get secure buttons, other plugins would still get their standard one.
- a "callback" or "OnCreate" field, supplied by the plugin that contains a function that the display would call upon creation of the button with the button reference as first argument. (This is needed by the plugin to initialize attributes before the user can interact.)
EDIT: removed the secure _ondrag* attributes stuff, it's not a drawback :)
Problem implementing this is that it isn't part of the LDB definition. I'm a bit vary of adding special hacks to support something like this. Perhaps it'd be better to discuss the implications and implementation details in a general LDB thread?
Problem implementing this is that it isn't part of the LDB definition. I'm a bit vary of adding special hacks to support something like this. Perhaps it'd be better to discuss the implications and implementation details in a general LDB thread?
Definitely. This sounds like a possible spec-update, and I'd hope this would be under general concensus rather than a Microsoft-style "because we want to do this, and we don't care about the spec" action.
the only bug I found is that at some point, when I increase the bin width the addons from the second line don't go into the first even if they have the space to do so.
Problem implementing this is that it isn't part of the LDB definition. I'm a bit vary of adding special hacks to support something like this. Perhaps it'd be better to discuss the implications and implementation details in a general LDB thread?
Definitely. This sounds like a possible spec-update, and I'd hope this would be under general concensus rather than a Microsoft-style "because we want to do this, and we don't care about the spec" action.
Sure, as I posted in the SBC thread: more display may want to allow secure buttons and I think we should standardize the field names and extend the LDB spec (It's probably been made extensible just to support secure stuff !!;):rolleyes:).
I made a vague request in the LDB thread 2 days ago, but got no answer at all, so I contacted LDB display authors instead :p
There is no need to extend the basic LDB spec. You are basically asking display authors to support a/your custom LDB spec. To be perfectly honest, I'm not that crazy about secure buttons as LDB objects, it creates a huge headache of possible issues with the buttons been created with proper handlers so that that won't taint every second, plus it's an implementation mostly suited for action buttons/action bars/action whatever rather than data feeds, but I'm willing to see how you picture this working.
I don't know why LBD would need secure buttons either - I mean, how often is that really necessary in a LDB addon. I.e.: why does it need to be LDB, and at the same time have secure buttons?
The main point from me would be, I can't see a case where I'd need secure buttons in the LDB display. Ever.
There is no need to extend the basic LDB spec. You are basically asking display authors to support a/your custom LDB spec. To be perfectly honest, I'm not that crazy about secure buttons as LDB objects, it creates a huge headache of possible issues with the buttons been created with proper handlers so that that won't taint every second, plus it's an implementation mostly suited for action buttons/action bars/action whatever rather than data feeds, but I'm willing to see how you picture this working.
I was asked what could use secure stuff, and I gave concrete exemples with my addons. But give the possibility and you will see other authors that will start to make use of it. It's just a matter of time. (Exploring all the possibilities, always trying to achieve what was impossible before, is what I think is so great about programming :p)
I see many addon authors that cower in fear when they hear "secure" and only think of taint issues and horribly complexe implementations. Let's prove they are dead wrong. As of 3.0, secure stuff has never been so easy and flexible to use. Also, Alestane and Iriel released a very detailed guide for everyone to start using it from scratch.
I really want LDB to be more than just text and config shortcuts. You can largely widen the possibilities in a few lines! Ever wanted to promote LDB over *similar* addons ? Be the first to implement this! (Damn Im so bad to sell the idea it hurts :p)
I would love to sell the idea honestly, I'd like to believe I'm open minded and all that :p but all I've seen so far is some basic examples. Can we have the custom spec outlined for us please or at least a very rough idea so we can brainstorm and discuss it. For instance, what kind of attributes do we need in the LDB object (I've seen 2-3 so far explained), which ones are displays going to use, which ones will be used purely by the DO. What is the proposed way that a display goes about "detecting" the spec (let's say set type attribute to "secure object"), does the display need to fire/register callbacks and if yes when and how (I've seen so far that the display may/will need to detect and call a func defined by the DO). This is the kind of thing I'm talking about when I say "outline the spec". Without this plus some solid, useful examples (call me weird but using tradeskills or applying weapon buffs when I'm fighting a mob that is about to eat me for breakfast isn't exactly very common, on the other hand let's say storing target(s) on a button/block is something that may interest me), this is all vaporware.
I would love to sell the idea honestly, I'd like to believe I'm open minded and all that :p but all I've seen so far is some basic examples. Can we have the custom spec outlined for us please or at least a very rough idea so we can brainstorm and discuss it. For instance, what kind of attributes do we need in the LDB object (I've seen 2-3 so far explained), which ones are displays going to use, which ones will be used purely by the DO. What is the proposed way that a display goes about "detecting" the spec (let's say set type attribute to "secure object"), does the display need to fire/register callbacks and if yes when and how (I've seen so far that the display may/will need to detect and call a func defined by the DO). This is the kind of thing I'm talking about when I say "outline the spec". Without this plus some solid, useful examples (call me weird but using tradeskills or applying weapon buffs when I'm fighting a mob that is about to eat me for breakfast isn't exactly very common, on the other hand let's say storing target(s) on a button/block is something that may interest me), this is all vaporware.
Let's discuss about it in the LDB thread. Thought Im not gifted with words and will have to chose them carefully. It's hard if you're not fluent in english, and as some philosopher said: "people forgive more easily bad actions than bad mouthing" :p
I couldn't find it on wowinterface.com - only "Ara Broker Guild Friends" and "Ara Dotimer"...
It has yet to be released, there's alot of polishing to do before and maybe a redesign of the way to handle tradeskill CDs (there's alot of mouse/modifier combo in the shadow if you wanna try that alpha version :p).
I couldn't find it on wowinterface.com - only "Ara Broker Guild Friends" and "Ara Dotimer"...
Yeah it's gone now, I think (well actually I read a few posts up) the author wants to develop it some more. I guess I was lucky to catch it when I did :)
Odd - I have Broker_Professions, and I could swear it works in combat. Granted I've never tried to build a Helicopter while healing an Archimonde raid, but I could swear it works. Just odd.
Hrm, if tradeskills don't work, that'd be a real case for Secure Buttons. However my comment from before remains: Does it need to be LDB? (see TradesBar for example)
The main reason for asking this is that from what I understand it'd be a huge addition and would likely (?) cause considerably code-bloat in the process.
And if the gains are fairly limited in total number I'd find it codewise smarter to use specialized addons for those cases and keep LDB lean and mean. If that makes sense.
Some kind of visual feedback would help with this.
I'll investiage the possibility of making secure buttons work in ButtonBin (most likely on a per-bin level). The drawbacks of course is that things can't be moved or resized during combat which would require some tweaking.
Secure stuff would need some communications between the plugin and the display. Using fields on the data object would be the perfect place:
- a "secure" or "secureTemplate" field, supplied by the plugin to provide the template(s) string, used by the display as the 4th argument of CreateFrame. That way, only plugins that provide a template field would get secure buttons, other plugins would still get their standard one.
- a "callback" or "OnCreate" field, supplied by the plugin that contains a function that the display would call upon creation of the button with the button reference as first argument. (This is needed by the plugin to initialize attributes before the user can interact.)
EDIT: removed the secure _ondrag* attributes stuff, it's not a drawback :)
Definitely. This sounds like a possible spec-update, and I'd hope this would be under general concensus rather than a Microsoft-style "because we want to do this, and we don't care about the spec" action.
the only bug I found is that at some point, when I increase the bin width the addons from the second line don't go into the first even if they have the space to do so.
Sure, as I posted in the SBC thread: more display may want to allow secure buttons and I think we should standardize the field names and extend the LDB spec (It's probably been made extensible just to support secure stuff !!;):rolleyes:).
I made a vague request in the LDB thread 2 days ago, but got no answer at all, so I contacted LDB display authors instead :p
The main point from me would be, I can't see a case where I'd need secure buttons in the LDB display. Ever.
I was asked what could use secure stuff, and I gave concrete exemples with my addons. But give the possibility and you will see other authors that will start to make use of it. It's just a matter of time. (Exploring all the possibilities, always trying to achieve what was impossible before, is what I think is so great about programming :p)
I see many addon authors that cower in fear when they hear "secure" and only think of taint issues and horribly complexe implementations. Let's prove they are dead wrong. As of 3.0, secure stuff has never been so easy and flexible to use. Also, Alestane and Iriel released a very detailed guide for everyone to start using it from scratch.
I really want LDB to be more than just text and config shortcuts. You can largely widen the possibilities in a few lines! Ever wanted to promote LDB over *similar* addons ? Be the first to implement this! (Damn Im so bad to sell the idea it hurts :p)
Sorry to get off-topic here, but will you be publishing this addon? It looks to be almost exactly what I am after for my tradeskills. :)
Let's discuss about it in the LDB thread. Thought Im not gifted with words and will have to chose them carefully. It's hard if you're not fluent in english, and as some philosopher said: "people forgive more easily bad actions than bad mouthing" :p
It has yet to be released, there's alot of polishing to do before and maybe a redesign of the way to handle tradeskill CDs (there's alot of mouse/modifier combo in the shadow if you wanna try that alpha version :p).
Yeah it's gone now, I think (well actually I read a few posts up) the author wants to develop it some more. I guess I was lucky to catch it when I did :)
Hrm, if tradeskills don't work, that'd be a real case for Secure Buttons. However my comment from before remains: Does it need to be LDB? (see TradesBar for example)
The main reason for asking this is that from what I understand it'd be a huge addition and would likely (?) cause considerably code-bloat in the process.
And if the gains are fairly limited in total number I'd find it codewise smarter to use specialized addons for those cases and keep LDB lean and mean. If that makes sense.
type = icon
We have font, background, border, sound
The main Button Bin config page (click on the bin icon or go to the normal interface->addon settings) has a toggle to unlock tbe bars.