Going to the logging window, selecting Manual Entry, and attempting to enter roasting data by hand in the table view does not work. As the feature exists right now, there's very little reason to keep it as it was never well integrated, accessing that through a window that generally depends on being connected to something that can log roasting data automatically makes very little sense, and people have not been trying to use this feature.
It does, however, make sense to provide a way to manually enter batch data into the roasting log in order to use Typica's database for some of the surrounding functionality. Sample roasting is a major example as many use sample roasters with designs that effectively prevent meaningful instrumentation. Investing in hardware retrofits just for being able to use Typica on a machine that would not generate useful roasting data is a poor value proposition and with some machines would not be practical even if it were affordable. This would also provide a way for people to try using more of Typica's features before investing in hardware for automated logging on machines where that would make more sense.
A manual log entry option also seems like a good place to provide hooks for importing roasting data collected by other programs.
N3Roaster
commented
7 years ago
Going to the logging window, selecting Manual Entry, and attempting to enter roasting data by hand in the table view does not work. As the feature exists right now, there's very little reason to keep it as it was never well integrated, accessing that through a window that generally depends on being connected to something that can log roasting data automatically makes very little sense, and people have not been trying to use this feature.
It does, however, make sense to provide a way to manually enter batch data into the roasting log in order to use Typica's database for some of the surrounding functionality. Sample roasting is a major example as many use sample roasters with designs that effectively prevent meaningful instrumentation. Investing in hardware retrofits just for being able to use Typica on a machine that would not generate useful roasting data is a poor value proposition and with some machines would not be practical even if it were affordable. This would also provide a way for people to try using more of Typica's features before investing in hardware for automated logging on machines where that would make more sense.
A manual log entry option also seems like a good place to provide hooks for importing roasting data collected by other programs.