Re: Setting System brightness Above 255?
Posted: 27 Apr 2019 21:44
Your replies are always so long
So anyway, by common practice, do you mean preferences (such as curly brace placement)?
From your previous reply, I already do understand what you meant by your concept of "flow variables", but I just don't see why you would not just use a Global Variables instead.
Perhaps it will be somewhat helpful since it can be stored in a separate place and not clutter up the list of global variables, but other than that, performance will probably just be the same. How exactly would making it restricted to one flow make it only slow down that flow and not the others? Plus, it'll be restricted to for use in only one flow which might be a bad idea, since some tasks can take more than just one.
If you need to log large amounts of data, why not just export it to multiple separate files (such as by day) like you said? If you separate the files, it'll make it much easier and faster to handle them.
As for calculating the range for multiple devices, are you sure it's a good idea to do this? If we just have the user write down the different ranges for when auto brightness is on or off, for example, we could just switch between them since they'd be stored in a map. Converting them would make no sense, since we have no way to tell what the other range the device use would be. If the user can te you the range, they should also be able to just give you the min and max values. From there, we just have to worry about how much to increase/decrease by each time the vume buttons are pressed.
So anyway, by common practice, do you mean preferences (such as curly brace placement)?
From your previous reply, I already do understand what you meant by your concept of "flow variables", but I just don't see why you would not just use a Global Variables instead.
Perhaps it will be somewhat helpful since it can be stored in a separate place and not clutter up the list of global variables, but other than that, performance will probably just be the same. How exactly would making it restricted to one flow make it only slow down that flow and not the others? Plus, it'll be restricted to for use in only one flow which might be a bad idea, since some tasks can take more than just one.
If you need to log large amounts of data, why not just export it to multiple separate files (such as by day) like you said? If you separate the files, it'll make it much easier and faster to handle them.
As for calculating the range for multiple devices, are you sure it's a good idea to do this? If we just have the user write down the different ranges for when auto brightness is on or off, for example, we could just switch between them since they'd be stored in a map. Converting them would make no sense, since we have no way to tell what the other range the device use would be. If the user can te you the range, they should also be able to just give you the min and max values. From there, we just have to worry about how much to increase/decrease by each time the vume buttons are pressed.