by Alt » Thu Oct 29, 2015 9:21 am
We would like to clarify some points on this matter. Our technician could not provide data-medics ( with access to older versions of R-Studio because we typically do not provide our customers with old versions of our software and our support team does not have such access either. The technician had to contact his supervisor and our developers to fulfill the request. Nevertheless, data-medics was provided with the requested links within one and half hour.
Also, we checked the current R-Studio for Linux build on different computers in our lab with a similar software configuration but we were unable to reproduce the issue, as well as no one else has reported it to our techsupport. We haven’t received any additional clarifications from data-medics and he still hasn't reported if there was the same
issue with the old R-Studio for Linux build or not. In accordance with our developer's report, the program module that might behave so strange has not been changed for a while.
For now we are considering the issue as a specific glitch on a specific machine that could appear because of conditions that couldn’t be simulated in our testing lab.
We would like to clarify some points on this matter. Our technician could not provide data-medics ( with access to older versions of R-Studio because we typically do not provide our customers with old versions of our software and our support team does not have such access either. The technician had to contact his supervisor and our developers to fulfill the request. Nevertheless, data-medics was provided with the requested links within one and half hour.
Also, we checked the current R-Studio for Linux build on different computers in our lab with a similar software configuration but we were unable to reproduce the issue, as well as no one else has reported it to our techsupport. We haven’t received any additional clarifications from data-medics and he still hasn't reported if there was the same
issue with the old R-Studio for Linux build or not. In accordance with our developer's report, the program module that might behave so strange has not been changed for a while.
For now we are considering the issue as a specific glitch on a specific machine that could appear because of conditions that couldn’t be simulated in our testing lab.