On Thu, 17 Dec 2009, Przemysław Czerpak wrote: hi,
> > the symptom is that when there is already data in the primary when > > this app is started, the first inkey(0) is immediately satisfied (and > > then it shows the correct content for the primary selection). > > > > this doesn't happen absolutely always, but it does most of the time. > > if the primary is empty at app startup, then it never happens. this one is solved,, thank you. > > so the guess it that *something* is there that causes clients to exit > > unexpectedly. it is not even sure that the client that exits is the this one is not. > Your VM crashes when selection owner does not response. I'll add code > to disable own selection in GTXWC exit phase and I hope it will help > anyhow real fix should be done in WM code because your description > suggests that it may have very serious problems and even crash if > selection owner terminates suddenly without clearing the selection > i.e. due to delivered asynchronous signal (killall myapp). thanks for the explanation. never mind about the second issue just yet, i will bring it up with wm people. thanks, -- [-] mkdir /nonexistent _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
