-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Porting to Gtk3 and fixing vte failure #4
Conversation
Thanks. Please explain why you are removing the reference to the VTE class yet leaving the VTE class in the file? The VTE class contains quite a bit of functionality. Please also detail the testing you did. |
Thanks for reviewing I realized the big mistake I did by removing the reference to the VTE class, thus |
Thanks. Reviewed. Please learn about the activity as much as you can in order to test. You'll need to be familiar with VNC technology and tools. |
Tested the activity, runs fine on my machine with os Ubuntu 18.04.I request you to test once more. |
Thanks. Tested 7249288 on Ubuntu 18.04. The activity did not start. Log output;
|
Quite surprising for me, showed no such error on my machine, I don't know the reason why it happened, but logically the error is quite clear, so made changes accordingly and pushed the changes.Again since it made no difference on my machine I am not able to ensure that it works, it needs to be tested. |
Thanks. Tested d4f75fe. Does start now. Fixes #2. Fixes #3. Doesn't fix #1 but will help. Doesn't fix #7. I've never used this activity before; I would have recognised the strange layout; Comments and suggested changes;
Please fully test the activity before asking for review. Did you use the start and stop buttons? |
Thanks for reviewing.
As I stated before running the activity on my machine do not show any errors, and its quite surprising for me as well, and for the same reason I am not able to properly test the activity.Though will look into it thoroughly and will work on the changes you suggested. |
Thanks. I'm certain I've tested the activity in the way that an end-user of Sugar would try to use it. If you cannot reproduce these errors, then there is something about your test environment or method that is different to mine. Please provide more information; e.g.
Also add some check of your own devising to make sure you are testing the same source code as you are editing; a simple method is to change one of the messages (such as "Exit VncLauncher Activity"), and look for the change when you run the activity. Remember not to |
Thanks. Surprisingly there was something wrong with Linux Distribution. Running |
Fascinating, thanks. But I'm not sure we learned anything. You could look at |
Stale. Closing |
The activity was in gtk and the conversion to sugar3 assumed no changes were needed between vte and Vte.
Porting to Gtk3 and making the desired changes.
Fixes #3 #2