| 
     
      
      
      From: Olivier C. <oli...@fr...> - 2000-09-30 21:52:08
      
     
   | 
Mikhael Goikhman wrote: > > On 29 Sep 2000 23:05:14 +0200, Olivier Chapuis wrote: > > > > TODO worte: > > > > * settings@default: think which subcomponents to remove/move. > > > Move settings/stroke@ to bindings@ option. > > > > Maybe, but why do you want to move stroke. Now I see stroke > > as a general config option since it an half external to FVWM. > > One of the reasons is that currently it is impossible to add stroke > bindings and redefining of existing ones is half-fixed. > What about a support for extra-stroke? or may be if one cp settings/stroke/* in its $userDir/themes/default/ dir then this one is read in the place of the site files but the others settings (and default component) are read from the site dir? Maybe this logic can be applied to all files. > With an option this would be possible. But then probably we first need to > rethink the option/choice/subcomponent concepts to make it possible for > components to reuse existing properties of other components. > > BTW, I want to rename 'choice' to 'variant' as less confusing, and use > choice as a general name for options and variants. Better naming? > for me it is ok. > > > * Fix all crashes. > > > > This is the most important point. I will try to work on this. > > In fact it will be great if Dominik works on this ... > > This is the main reason there is no 0.4.0 yet. > There are two serious problems on my computers. > > The first box is a mixed system with glibc-2.1.91 & XFree-4.0.1. There are > no core dumps on this computer except for known ones, like core of IconMan > in blackbox theme). But there is total X freeze when using some FvwmScript > modules with widgets outside of the window. Maybe we can fix the scripts > of these modules? This is a bug in XFree, but for us it is a feature. > Do you sent a bug report to XFree? I've modified FvwmApplet-Mixer so that now there are no widgets out of the window. So now I think that there are no scripts with widgets out of the window (DigitalClock has its widget of the same size of the window). A point is that ItemDraw does not support "clic", if it was so I think that we will be able to do very good applets. I think this will be very easy to implement, but fvwm is feature locked. Maybe you can send a bug report on this (ItemDraw does not support "clic") and I will do the implementation :o) > The second box is of my wife, RH 6.2, glibc-2.1.3. There are always core > dumps in malloc.c when switching themes. No core dumps otherwise. This is > very hard to spot, since the stack does not help (it is different for > every core). Something wrong with a memory, bug in fvwm or in glibc. > She will install RH 7.0 in a day or two, so I will probably not be able > to work on this problem if the newer glibc it better. > > Any other problems? Do you have core dumps? I have recently upgrade from a custom RH 5.1 to a Mandrake 7.1. The glibc is glibc-2.1.3-5mdk and I use gcc version 2.95.3 19991030 ... and I cannot succeed to get a core dump! And I try and try again :o) Before, with the RH, I used the glibc 2.0.7 and gcc 2.7.2.3 and I had a few core dumps with inconsistent core file as on your wife box (migo -> any). All these are very strange .... Olivier  |