From: Michiel N. <m.d...@he...> - 2011-07-06 19:30:22
|
Peter, I agree with you and Brian that two progress bars is not useful. But FamilyLines is not the only report that has two progress bars, there are several, for example BirthdayReport among the text reports. I don't mind to see the "Processing File" progress bar disappear. As for an explanation, I have non other than that threads make things much more complicated. I know, pretty lame. Michiel On 07/06/2011 10:53 AM, Peter Landgren wrote: > Michiel, > > I solved the users problem by temporarily deleting one of the progress bars. Now all three Graph > Reports behave identical. > But the issue is still there; why does it work on most systems, but not on some. > > And how useful is it to have two progress bars above each other? > > /Peter > >> Michiel, >> >> Thanks for answer. Yes, one progress bar is run in the main thread. This >> bar has different strings depending on what's going on. The other progress >> bar just says "Processing File" and the meter is just moving backwards and >> forwards and this one is run in the separate thread. You see only the >> first progress bar unless you move it so the underlaying will be seen. The >> other two reports just have this second bar and they work OK for the user. >> >> This seems to work on most systems , but not our users. >> >> I have no idea what to do. I could just for test purposes comment the bar >> in the main thread and see if the user get his Family Line Graph. >> >> /Peter >> >>> Hi Peter, >>> >>> I am not really the right person to answer this question, but I was >>> surprised to see that some reports are run in a separate thread >>> (function _run_long_process_in_thread in _reportdialog.py). The advice >>> on combining threads with gtk is to let the main thread do the GUI stuff >>> and use gobject.idle_add() in the created thread to schedule GUI >>> operations from the secondary thread. Gramps clearly doesn't follow this >>> advice. Perhaps that gives rise to the trouble. >>> >>> Michiel >>> >>> On 07/05/2011 12:51 PM, Peter Landgren wrote: >>>> Devs, >>>> >>>> I'm trying to help a user with a hanging problem. >>>> See http://www.gramps-project.org/bugs/view.php?id=5045 >>>> >>>> I think I have found the point in the code where the hanging occurs. >>>> >>>> In GVFamilylines.py, line about 425 I have added two print statements >>>> >>>> print "Close progress bar" >>>> self.progress.close() >>>> print "Progress bar closed" >>>> >>>> The first is executed , but the second is not in the users system. >>>> However in my system both strings are printed and all works just fine. >>>> >>>> The other two Graphs run without problem for the user. >>>> >>>> The only difference I can see is that GVFamilylines.py has two progress >>>> bars going on at the same time. See >>>> http://www.gramps-project.org/bugs/view.php?id=5073 >>>> >>>> Any idea of what's going on. I'm out of ideas now. >>>> >>>> /Peter >>>> >>>> ----------------------------------------------------------------------- >>>> -- ----- All of the data generated in your IT infrastructure is >>>> seriously valuable. Why? It contains a definitive record of >>>> application >>>> performance, security threats, fraudulent activity, and more. Splunk >>>> takes this data and makes sense of it. IT sense. And common sense. >>>> http://p.sf.net/sfu/splunk-d2d-c2 >>>> _______________________________________________ >>>> Gramps-devel mailing list >>>> Gra...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> >> --------------------------------------------------------------------------- >> --- All of the data generated in your IT infrastructure is seriously >> valuable. Why? It contains a definitive record of application performance, >> security threats, fraudulent activity, and more. Splunk takes this data >> and makes sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-d2d-c2 >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel > |