First I would like to thank you for providing this excellent tool. I just would like to say that the thin red line that tells which "window" is active, is a bit too thin. I also would like to know why we cannot get the last command with the up arrow on the console.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> I just would like to say that the thin red line that tells which "window" is active, is a bit too thin.
Hm. I guess this may depend on the screen resolution, your're working on. Perhaps we'll need a way to adjust this. Since I will not take care of this right away, could you submit a feature request for this (https://sourceforge.net/tracker/?group_id=50231&atid=459010)? This way the suggestion won't get lost.
> I also would like to know why we cannot get the last command with the up arrow on the console.
? This is supposed to work, and it works just fine, here. Could you try again? Perhaps it was a temporary problem of some sort (occasionally focus does not work correctly). Which version of rkward are you using?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>? This is supposed to work, and it works just fine, here. Could you try again? Perhaps it was a temporary problem of some sort (occasionally focus does not work correctly). Which version of rkward are you using?
I am using the version 0.4.7a on Kubuntu 7.10. Maybe is it a problem with Gutsy, since this version of Kubuntu is still an alpha release. In fact, I have to say that the problem does not occur systematically. It seems that it occurs when I send the current line from my script.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1- Run "print (1)" in the console
2- Enter "print (2)" in the script editor and run it (through the console)
3- Switch to the console, press up arrow, you will get "print (1)" again, instead of "print (2)".
Is this the situation you're referring to?
If so, I agree, this is rather confusing. I'll try to look into this, soon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's exactly the problem. I hope that you can fix it for the next release.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-05-01
Here's an open rant to the developers. Rkward has got to be the most unstable, unreliable package I've ever wrestled with. It crashes. It crashes for fun. It crashes in the sun. It crashes on Wednesdays. It crashes on all days. It crashes when I blink. It crashes when I think. I understand that it's *free*, and it looks like it could be an amazing tool. But it crashes so frequently that you really should call it "Awkward," or maybe the jokes on me. . .
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We take all feedback serious, even if it's in the form of a rant. Also, RKWard is known to crash once on each Wednesday.
However, the kind of crashing you claim to see is very likely a problem with a broken setup or a highly unusual use-pattern. If you give us some details, including information on your installed versions of R and RKWard, some more specific information on what you did just before your blinking caused RKWard to crash, possibly even a backtrace, or actually any useful information at all, we can almost certainly help you to a better user-experience.
In other words, please try to include at least a grain of information in your next rant, here or elsewhere.
Regards
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@6: I'm sure your problem is specific to your setup. Or perhaps you're running a very old version of RKWard? I've been running rkward for several years and I find it to be just as stable and reliable as any other (commercial or not) statistical program. Actually some commercial apps I work with are of remarkably low quality compared to rkward.
I can fully understand the frustration when things crash left and right, especially if the app looks as "sexy" as rkward and you really want it to work. But I would ask you to always treat the developers with respect. They are working hard and doing an awesome job from which the rest of us benefit so much.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First I would like to thank you for providing this excellent tool. I just would like to say that the thin red line that tells which "window" is active, is a bit too thin. I also would like to know why we cannot get the last command with the up arrow on the console.
Hi!
Thanks for your kind words.
> I just would like to say that the thin red line that tells which "window" is active, is a bit too thin.
Hm. I guess this may depend on the screen resolution, your're working on. Perhaps we'll need a way to adjust this. Since I will not take care of this right away, could you submit a feature request for this (https://sourceforge.net/tracker/?group_id=50231&atid=459010)? This way the suggestion won't get lost.
> I also would like to know why we cannot get the last command with the up arrow on the console.
? This is supposed to work, and it works just fine, here. Could you try again? Perhaps it was a temporary problem of some sort (occasionally focus does not work correctly). Which version of rkward are you using?
>? This is supposed to work, and it works just fine, here. Could you try again? Perhaps it was a temporary problem of some sort (occasionally focus does not work correctly). Which version of rkward are you using?
I am using the version 0.4.7a on Kubuntu 7.10. Maybe is it a problem with Gutsy, since this version of Kubuntu is still an alpha release. In fact, I have to say that the problem does not occur systematically. It seems that it occurs when I send the current line from my script.
I see. The problem is this situation:
1- Run "print (1)" in the console
2- Enter "print (2)" in the script editor and run it (through the console)
3- Switch to the console, press up arrow, you will get "print (1)" again, instead of "print (2)".
Is this the situation you're referring to?
If so, I agree, this is rather confusing. I'll try to look into this, soon.
That's exactly the problem. I hope that you can fix it for the next release.
Here's an open rant to the developers. Rkward has got to be the most unstable, unreliable package I've ever wrestled with. It crashes. It crashes for fun. It crashes in the sun. It crashes on Wednesdays. It crashes on all days. It crashes when I blink. It crashes when I think. I understand that it's *free*, and it looks like it could be an amazing tool. But it crashes so frequently that you really should call it "Awkward," or maybe the jokes on me. . .
We take all feedback serious, even if it's in the form of a rant. Also, RKWard is known to crash once on each Wednesday.
However, the kind of crashing you claim to see is very likely a problem with a broken setup or a highly unusual use-pattern. If you give us some details, including information on your installed versions of R and RKWard, some more specific information on what you did just before your blinking caused RKWard to crash, possibly even a backtrace, or actually any useful information at all, we can almost certainly help you to a better user-experience.
In other words, please try to include at least a grain of information in your next rant, here or elsewhere.
Regards
Thomas
@6: I'm sure your problem is specific to your setup. Or perhaps you're running a very old version of RKWard? I've been running rkward for several years and I find it to be just as stable and reliable as any other (commercial or not) statistical program. Actually some commercial apps I work with are of remarkably low quality compared to rkward.
I can fully understand the frustration when things crash left and right, especially if the app looks as "sexy" as rkward and you really want it to work. But I would ask you to always treat the developers with respect. They are working hard and doing an awesome job from which the rest of us benefit so much.