Closed FormidableYeti closed 3 years ago
interesting......
On Sat, Dec 26, 2020 at 9:16 PM FormidableYeti notifications@github.com wrote:
Feature request, make it easy for people to implement the control by locking the button name to functionality supported in code.
-OR- add options field that presents the functionality available in code so people can name the button whatever they want, but functionality works as called in code.
Decouple or lock button name functionality so end user has one less potential issue implementing button control, making control easier to support.
Options screen: Option Name: Button Function Options available (drop down list, single select control): Copy, Create CAB Request, etc
Functionality: Option makes button run code dedicated for its function.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/avih75/Action_Button_Control/issues/11, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIPBUI7DILMLRN3JP5ZEYV3SWYZBDANCNFSM4VKEPXYA .
-- בתודה, אבי חדד 0542400091
I did some changes..... added the requested things i hope i did ruined any
V 1.1.1.132
On Sun, Dec 27, 2020 at 10:49 AM Avi Hadad avih75@gmail.com wrote:
interesting......
On Sat, Dec 26, 2020 at 9:16 PM FormidableYeti notifications@github.com wrote:
Feature request, make it easy for people to implement the control by locking the button name to functionality supported in code.
-OR- add options field that presents the functionality available in code so people can name the button whatever they want, but functionality works as called in code.
Decouple or lock button name functionality so end user has one less potential issue implementing button control, making control easier to support.
Options screen: Option Name: Button Function Options available (drop down list, single select control): Copy, Create CAB Request, etc
Functionality: Option makes button run code dedicated for its function.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/avih75/Action_Button_Control/issues/11, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIPBUI7DILMLRN3JP5ZEYV3SWYZBDANCNFSM4VKEPXYA .
-- בתודה, אבי חדד 0542400091
-- בתודה, אבי חדד 0542400091
Very interesting. I had to update the settings and read the code a little to see what happened. I was a little confused with the options screen, but I appear to have figured it out.
One field it doesn't like is date/time - Microsoft.VSTS.Scheduling.DueDate
Adding the DueDate field causes error documented in the other github project ticket.
All options appear to work though without the duedate field included.
Its' pretty nice in that now this application appears really flexible.
I think only thing to do is clean up the Options Page a little. If it can do a drop down option for action type, that would help. I would also update tool tips., Like-
Button Name - This field will be what the button is named on your page.
Button Action Type - This is the action your button will perform.
hi you keep me busy ahh.....
so, i fix the date\time bug added the tooltip you asked
about the drop-down, i can see what you mean. but the idea of this control is to give you the option to set several buttons in the same control (copy, convert...). so it needs to be a free text for writing more than one Action name. second, i want it to be free text so i could build a specific action for my clients and hide it from the regular users.
On Mon, Dec 28, 2020 at 1:26 AM FormidableYeti notifications@github.com wrote:
All options appear to work though without the duedate field included.
Its' pretty nice in that now this application appears really flexible.
I think only thing to do is clean up the Options Page a little. If it can do a drop down option for action type, that would help. I would also update tool tips., Like-
Button Name - This field will be what the button is named on your page. Button Action Type - This is the action your button will perform.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/avih75/Action_Button_Control/issues/11#issuecomment-751528218, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIPBUI2LHVTO6IIFSR3ZYB3SW67DVANCNFSM4VKEPXYA .
-- בתודה, אבי חדד 0542400091
how about this. A drop down for action type, but for your specific clients, the code checks if they called the button name something specific.
For example, if button name = "Special function", then ignore button action type - go to specific code section to do work.
This way, you still have hidden section, but ease of use for general users, perhaps?
First, you didnt say any thing about the date time fix
Second, as i said, you can put two buttons in on control.... so a dropdown will limit me to one action
בתאריך יום ב׳, 28 בדצמ׳ 2020, 20:20, מאת FormidableYeti < notifications@github.com>:
how about this. A drop down for action type, but for your specific clients, the code checks if they called the button name something specific.
For example, if button name = "Special function", then ignore button action type - go to specific code section to do work.
This way, you still have hidden section, but ease of use for general users, perhaps?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/avih75/Action_Button_Control/issues/11#issuecomment-751816650, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIPBUIYAOZS5NWA5475RIHDSXDEAPANCNFSM4VKEPXYA .
Just tested - Date time fix is perfect, I'll go in update those requests to close out :)
I didn't think about multiple buttons in the control. I was thinking I would have to add the action control multiple times to the screen, but never tried to see if that was possible. perhaps yes, then it would need to be multiselect list, or something, but way it works now is good. Was just thinking about end users, but might be as easy to handle in how to use documentation.
new update, add action button as a widget
Feature request, make it easy for people to implement the control by locking the button name to functionality supported in code.
-OR- add options field that presents the functionality available in code so people can name the button whatever they want, but functionality works as called in code.
Decouple or lock button name functionality so end user has one less potential issue implementing button control, making control easier to support.
Options screen: Option Name: Button Function Options available (drop down list, single select control): Copy, Create CAB Request, etc
Functionality: Option makes button run code dedicated for its function.