Bug 380774

Summary:	PROBLEM IN R: Hard to stop locator() and identify(1)
Product:	[Applications] rkward	Reporter:	RKWard Team <rkward-devel>
Component:	general	Assignee:	RKWard Team <rkward-devel>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	All
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description RKWard Team 2011-12-13 13:17:34 UTC

-- Originally posted by (AT sourceforge.net): nalimilan --

-- This ticket was imported from http://sourceforge.net/p/rkward/bugs/116 on 2017-05-30 15:26:58 +0100 --
If you run locator\(\) without specifying a number, or identify\(1\) and can't select the required point for some reason \(it happened to me today\), you've no way obvious way of getting out of it, and R is blocked. It took me a few minutes to understand that right-click was a solution.

I think Esc should stop these commands, but also that Ctrl+C and the "Interrupt all commands" button should work too. Closing the dialog, moving to another graph, etc. should also stop them, instead of hanging.

\(One could also dream of integrating these commands into the dialog, but that's another issue. ;-\)

Comment 1 Thomas Friedrichsmeier 2011-12-13 17:31:10 UTC

Confirmed. However, the same happens when using a regular R console, outside of RKWard. This probably needs fixing in the X11 device. BTW, when trying to close the device in this situation, R 2.14.0 \(debian sid, i386\) crashes on me. At least we don't trigger the crash in RKWard...

Have you checked the R bug tracker for any matching reports, yet?

&gt; \(One could also dream of integrating these commands into the dialog, but that's another issue. ;-\)

Indeed. And it should be fairly easy to implement as a plugin. However, as long as these commands have such severe issues, it may not be a good idea to lure users into trying them...

Regards
Thomas

Comment 2 Thomas Friedrichsmeier 2011-12-13 17:31:11 UTC

- **summary**: Hard to stop locator() and identify(1) --> PROBLEM IN R: Hard to stop locator() and identify(1)

Comment 3 RKWard Team 2011-12-13 17:53:39 UTC

-- Originally posted by (AT sourceforge.net): nalimilan --
Ah, I could have checked. I'll look for reports and file a new bug if it isn't known.

\(But I don't experience the crash here on Fedora 15 x86-64, so you'll need to report it directly...\)

Comment 4 RKWard Team 2011-12-13 17:57:15 UTC

-- Originally posted by (AT sourceforge.net): nalimilan --
I should add: there's maybe a bug in RKWard in the sense that it blocks when trying to close the graph window. This probably prevents the crash on your machine, but it makes it impossible to stop locator\(\) this way.

Comment 5 Thomas Friedrichsmeier 2013-03-22 09:28:30 UTC

Small update: There is now a way (although somewhat ugly) to force-close a graph, and thus break out of locator() this way.

Comment 6 Thomas Friedrichsmeier 2016-01-01 19:11:27 UTC

- **status**: open --> closed-fixed
- **Group**:  --> CRASH

Comment 7 Thomas Friedrichsmeier 2016-01-01 19:11:28 UTC

Closing. The parts that are fixable on RKWard's side were fixed long ago (esp. being able to close an X11() window despite an active call to locator()). Ever since we have the RK() window, this is also much less of an issue, as this handles interrupting locator(), correctly, in the first place.

The part about integrating identify() and locator() in the plot window is now tracked at https://bugs.kde.org/show_bug.cgi?id=357402 .