Hi,
I'm running Tinn-R 1.19.4.7 with R 2.6.2 under Windows XP. R Gui is in SDI mode, and the Profile.site file under /etc is identical to that in the Tinn-R help file, except for the drive name of the Tinn-R directory, which is drive H: in my case. (R is on C: drive, but everything was working OK before this evening with this configuration.)
Tinn-R is suddenly failing to send commands from Tinn-R to R. I have observed three behaviours:
Nothing happens when I push the "submit line" button or use the menu sequence R > Send To R > line.
Using the menu sequence R > Send To R > line results in the current contents of the clipboard being inserted into the open R file at the point that the cursor happens to be.
Using either of these methods results in the current line being duplicated in the Tinn-R file I have open, and nothing gets sent to R. This only seems to happen in the second and subsequent files that are created (via the new file button) in a given Tinn-R session.
I have uninstalled and reinstalled Tinn-R, but this does not fix the problem. Any suggestions?
(I can send you a dump of my complete system configuration if you need it, but I'm unsure if attaching a 364 kb text file is allowed via this forum)
Regards,
Leon.
Logged In: YES
user_id=1273895
Originator: NO
Hello Leon,
I know this bug only if there is any other window (or process) with the caption 'Console'.
Please, check this possibility before to go ahead in this topic/discussion.
Due to the amount of GUIs that R recognizes (SciViews, JGR, and R Console) it is impossible to change the way as Tinn-R and the GUIs is done.
We've been working to release the version 1.19.5.0. I'll works also with Rterm (very hard work). The communication with Rterm is more specific (IPC-Pipe: Inter Process Communication named Pipe) and this problem will be solved. IT is already runing, but not complete yet.
Let me know if the above is the origin of the problem.
All the best,
JCFaria
Logged In: YES
user_id=1408090
Originator: YES
Hello again, Jose.
Unfortunately I can find no other windows or processes with the caption "Console". ( I looked in Windows Task Manager under the processes tab for the processes: is this correct?).
I experienced a further difficulty: starting Tinn-R by itself brought up this error:
Access violation at address 006C1948 in module 'Tinn-R.exe'. Read of address 0000008
I'm not sure if this is any help to you.
I also tried a system restore to a point a few weeks ago when Tinn-R was working OK with R. But this has not helped. However, the access violation message no longer occurs.
I'm not sure I understand what Rterm is. Perhaps I should wait until version 1.19.5.0.
Thank you for your time so far,
Leon.
Logged In: YES
user_id=1408090
Originator: YES
Greetings Jose,
Just a quick note to let you know that the strange behaviour described in my original message has now disappeared. It appears that a trojan was messing with something. Once I got rid of the trojan, things returned to normal (almost).
The only odd behaviours are:
when I use the sequence File>Open and move the mouse into the areas of the dialog box to select a file, Tinn-R hangs. I can work around that, but I presume something that Tinn-R requires go removed in the process of cleaning-up after the trojan
The irritating behaviour reported also in one of the forums about the pasting of text into a Tinn-R file once you get to the bottom of the first screen's worth of text. I presume that will be fixed in the next version?
Cheers,
Leon.
Logged In: YES
user_id=1273895
Originator: NO
"Just a quick note to let you know that the strange behaviour described in
my original message has now disappeared. It appears that a trojan was
messing with something. Once I got rid of the trojan, things returned to
normal (almost)."
Dear Leon,
Well... good news!
"1. when I use the sequence File>Open and move the mouse into the areas of
the dialog box to select a file, Tinn-R hangs. I can work around that, but
I presume something that Tinn-R requires go removed in the process of
cleaning-up after the trojan"
I think it is not related with the Tinn-R but with your Operational System!
Perhaps it was a bit corrupted by the trojan!?
"2. The irritating behaviour reported also in one of the forums about the
pasting of text into a Tinn-R file once you get to the bottom of the first
screen's worth of text. I presume that will be fixed in the next version?"
Yes, it was!
The bug was related with the main component (SynEdit) used. The SynEdit team worked to fix this bug.
The new Tinn-R version will be 2.0.0.1 (with a lot of changes, more power, flexibility and simplicity).
All the best,
JCFaria