John McCabe-Dansted wrote: > >> #6427. On my machine each threaded export has a roughly 50% chance of > >> crashing LyX. We don't need users tell us that EXPORT_in_THREAD is > >> broken. We already know it is. > > Actually, I think I am hitting #6516 more often than #6427.
i see. the master child layout and viewing seems to be really killer for lyx even here. priority raised. > But we have already caught/reported this bug. I am not sure how making > a users window disappear would help us further. for this one no ;) > It seems that a dialog box allowing the user to choose what to do on a > case by case basis would be nicer than the LyX window disappearing > without any warning. Is there a disadvantage? over engineering. please note again that alpha is for testers only and not for Joe the BFU. the annoucements will go only to dev and users list. the dialog which would make me interested is the one which produce backtrace after each crash, so user can put it in our bugzilla. but thats not easy to do i guess. > Well how about the search option? As a tester an option to quickly > tell whether a bug has already been reported would seem quite useful. > > Also the report option could inform the user that if they do not know > how to reproduce the bug they need not report it. FYI, I have search > and report links in keytest like this: > http://gmatht.homelinux.net/xp/html_out/out/t4/html/ > The report fills in a "How to reproduce" stub that may also encourage > the user to look for a way to reproduce. (Since I am currently the > only user of keytest this is hardly necessary for keytest yet). sorry John, really better to focus on fixing the particular bugs then this circus around :) pavel
