[01:46] <manusheel_> neeraj: http://bugs.sugarlabs.org/ticket/1442
[01:47] <manusheel_> http://bugs.sugarlabs.org/ticket/2195
[01:56]  * dfarning is away: Away
[01:56]  * dfarning is back (gone 00:00:13)
[16:31]  * dipankar is away: Be Right Back
[16:34]  * ishan is away for dinner
[16:40] <manusheel> mukul: Hi Mukul.
[16:40] <mukul> hi sir
[16:40] <mukul> hi alsroot
[16:40] <alsroot> mukul: hi
[16:45] <manusheel> mukul: Did you get a chance to send the documentation on the analysis and implementation plan for the bug assigned to you?
[16:45] <mukul> manusheel sir: I will do that in some time.
[16:47] <manusheel> mukul: Ok.
[16:47] <mukul> alsroot, http://paste.ubuntu.com/496530/ please have a look
[16:48] <mukul> alsroot, I am trying to add a Continue button in the modal dialog which on clicking will take us to the main view
[16:50] <alsroot> mukul: and whats the problem?
[16:51] <mukul> alsroot, I have reproduced the error by making some adjustments to the variable. Also, to display the message only once, I've added this code. But it does not do the desired thing. http://paste.ubuntu.com/496532/
[16:51] <mukul> alsroot, Sorry I forgot to mention. I was looking at the sl bug #630
[16:51] <ubot2> Launchpad bug 630 in baz "default directory name contains unnecessary and outdated information" [Medium,New] https://launchpad.net/bugs/630
[16:53] <alsroot> mukul: so you plan is showing alert dialog only once?
[16:54] <alsroot> *your
[16:56] <mukul> What I plan to do is: Add a Continue button in the modal dialog box. Also, there should be a way to come back to the Main View. So now what happens is that when I return by pressing F3. it shows the dialog again. So I have modified the code. But it is not being implemented properly
[16:58] <mukul> alsroot, I will be back in 5 mins.
[17:00] <alsroot> mukul: I guess continue button might just close dialog (to return to current view)
[17:04]  * ishan is back
[17:17] <mukul> alsroot, Yes that is what I want to implement. What changes should I make in the 15-19 lines
[17:21] <alsroot> mukul: I guess you'll have to modify the code where ModalAlert appears, look like this code shows the journal not ModalAlert itself
[17:27] <mukul> alsroot, This code I found out in the file ModalAlert.py
[17:27] <mukul> Ok I'll grep it and find some other files too
[17:30] <alsroot> mukul: just grep for "ModalAlert()"
[17:44]  * dipankar is back (gone 01:12:05)
 alsroot, that is the only place where the ModalAlert() is called. Either the problem lies in the code mentioned by me or something is wrong in the function itself.
 alsroot, There has to be sthing wrong in the code itself
 manusheel, alsroot : http://paste.ubuntu.com/496532/ Here I think the value of i is always initialised to be 1 and thus no change in output. Do I have to define sthing like extern variable so that its value does not chang
[20:45] <neeraj> #sugar
[20:46] <manusheel> neeraj: Hi Neeraj.
[20:47] <neeraj> manusheel: Hi sir
[20:47] <manusheel> neeraj: Any help needed on that gtk icon issue?
[20:48] <ishan> manusheel, sir that didnt worked as my cpsection is not opening up
[20:49] <neeraj> manusheel: Sir, I will start working from where I left last night. Will ask in case of any doubt.
[20:49] <manusheel> neeraj: Sure..
[20:49] <neeraj> I slept whole day, so will remain awake for next 4-5 hrs :)
[20:49] <manusheel> neeraj: Sure.
[20:50] <manusheel> ishan: Ok.
[20:50] <dfarning> neeraj nice work last night:)
[20:51] <manusheel> ishan: Where are you facing issues?
[20:52] <neeraj> dfarning: thanks.. Still in learning phase w.r.t to pygtk. Hopefully I will pick up things quickly. This bug has made me study python, pygtk and lots of sugar code and helped in learning new things :)
[20:52] <manusheel> neeraj: Can you help Ishan on this a bit. In a meeting right now. Ishan, I'll be back soon.
[20:52] <ishan> manusheel, after making changes and rebuilding sugar-jhbuild when i right click and click on settings it doesnt open ups
[20:52] <neeraj> ishan: what problem are u facing?
[20:52] <ishan> neeraj, ^^
[20:52] <ishan> working on http://bugs.sugarlabs.org/ticket/245
[20:53] <neeraj> hmm.. ishan what changes did u made?
[20:53] <dfarning> neeraj. yep you jumped in the deep end and survived... that is the sign of a good hacker:)
[20:55] <neeraj> ishan: where did u added the code?
[20:55] <ishan> neeraj in buddymenu.py
[20:56] <ishan> but i dont think that should be the file since if we add the code there it wil show busy worker when we click on my setting but whereas we want it to show when we click on languages under cpsection
[20:59] <neeraj> ishan: ok. that newly added line caused the problem.. That 100% sure.
[20:59] <ishan> yep
[21:00] <ishan> neeraj:i just took some points from the patch made by anurag sir on displaying busy cursor for logging and shutdown options
[21:00] <neeraj> ishan: ok.. reading the bug details on bugs.sugarlabs
[21:00] <ishan> neeraj okay
[21:03] <neeraj> ishan: Ok. Wish if u can also tell me the bug number on which anurag was working.
[21:03] <ishan> neeraj:2151
[21:04] <neeraj> ishan: As the bug description say's that we want the cursor to display when we select the language option. Do we need it any other cpsection menu ?
[21:04] <ishan> neeraj: as mentioned in the bug filed i dont think so
[21:05] <neeraj> ishan: Ok.
[21:07] <ishan> neeraj, aby pointer on above problem?
[21:07] <ishan> aby/any
[21:08] <neeraj> ishan: yes. wait a min
[21:08] <ishan> neeraj, sure
[21:10] <neeraj> ishan: are you sure that code will work? I mean anurag has mentioned that the patch failed to work.  http://bugs.sugarlabs.org/ticket/2151#comment:4
[21:10] <neeraj> Also, Ishan, I think you might need to modify the gui.py file in jarabe/controlpanel
[21:11] <ishan> neeraj, okay
[21:11] <neeraj> because, from here we choose the option and call the respective cp section menu.
[21:11] <ishan> neeraj, +1
[21:12] <neeraj> ishan: one solution which is coming to my mind is that we can add a condition that if current option ==language, then show the busy cursor
[21:15] <dfarning> neeraj, for simplicity how about switching to  busy cursor every time?  the user just wont see the change unless something is slow.
[21:17] <neeraj> dfarning: yes. that we can do. But I was not sure whether we could do this. I mean for simplicity add that in every item. :).