Closed dilomo closed 3 years ago
arendvw
commented
3 years ago I'm not against it.
Main reason there's an enable button is that it's faster for development of the plugin (toggle button works faster than enable/disable). And in earlier versions it needed more 'restarts', so a toggle was 'needed'.
dilomo
commented
3 years ago Yeah better not bother if it works for now. And hiding the enable would not be very grasshopper way so i decided to close this.
On Mon, 30 Aug 2021, 03:48 Arend van Waart, @.***> wrote:
I'm not against it. Main reason there's an enable button is that it's faster for development I guess :)
Might make it simpler.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/arendvw/ScriptParasite/issues/9#issuecomment-907848739, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO67N7XTHN2TXLXH7QNDJFLT7J6H3ANCNFSM5C2HV7EA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
arendvw
commented
3 years ago Cool, that's clear, I'll close this issue.
@arendvw I got another idea, more like proposal rather than a bug. What if we remove the Enable button switch so that the component becomes one line only? Enabling and disabling would be done with regular context actions of GH and the component will show disabled if no folder or in group with a script? Maybe I can try these days to see if would be okey usability wise..