It was just a suggestion, offered in good faith, and intended to help with the perennial question, "I changed the factor, did an 'update' and nothing happened ...". From my perspective, some extra canned text, set up once, is far preferable to having to give the same explanation multiple times. It can be trimmed to whatever is deemed suitable.
Christian Beer wrote:
... but I agree three times the same warning is also a bit too much.
You save space from just having a single warning but, even more importantly, you don't want to scare people away from running GPU tasks in the first place by having an overly dire warning that doesn't explain why it's **Dangerous**. In my experience, running BOINC using all available CPU threads, period, is more deserving of warnings about the potential for long term damage.
Christian Beer wrote:
Since this is also a more technical problem could you please open an issue in our Drupal issue tracker with that?
I went to the linked page to try to do as requested. I couldn't find any link there which would allow a visitor like me to 'open an issue'. I presume I would need to register somewhere and then 'log in' to find a way to do this. I don't have the skills or the time to make a contribution there so I don't particularly want to create yet another account somewhere. If you don't want to lose track of this, feel free to 'open an issue' any way you like. If it's not really seen as an issue, please just ignore it.
Christian Beer wrote:Gary,
)
It was just a suggestion, offered in good faith, and intended to help with the perennial question, "I changed the factor, did an 'update' and nothing happened ...". From my perspective, some extra canned text, set up once, is far preferable to having to give the same explanation multiple times. It can be trimmed to whatever is deemed suitable.
You save space from just having a single warning but, even more importantly, you don't want to scare people away from running GPU tasks in the first place by having an overly dire warning that doesn't explain why it's **Dangerous**. In my experience, running BOINC using all available CPU threads, period, is more deserving of warnings about the potential for long term damage.
I went to the linked page to try to do as requested. I couldn't find any link there which would allow a visitor like me to 'open an issue'. I presume I would need to register somewhere and then 'log in' to find a way to do this. I don't have the skills or the time to make a contribution there so I don't particularly want to create yet another account somewhere. If you don't want to lose track of this, feel free to 'open an issue' any way you like. If it's not really seen as an issue, please just ignore it.
Cheers,
Gary.