> On 14 Sep 2004, Mark Gray wrote: >> I am writing a fvwm perl module and anticipate wanting to parse the >> window_flags data upon receiving each M_ADD_WINDOW event. Looking >> through the FVWM perl modules I did not see any function for doing >> this, and before going to the trouble to translate the bit-fields in >> fvwm.h to perl I thought I would ask if it has already been done (and >> I just didn't look hard enough:-) This will be my first FVWM perl >> module so I apologize if this is a FAQ.
Salvatore Domenick Desiano <[EMAIL PROTECTED]> writes: > Unfortunately, the flag locations differs from platform to platform and > from compiler to compiler. If you (or anyone) wanted to write a robust > version, it would have to do a compile of a C program during the build of > fvwm, and produce some perl code from the result. > > I've done it for individual flags, but my process is entirely manual > because I'm only using two or three flags. Yes, I realized the difficulties involved in a Perl only solution, which is why I had hopes it was already done for me :-) While I was sleeping I came upon a simpler, but less general solution to the problem I was trying to fix: Since I know the names and classes of the Windows I want to treat in a special manner, there is no need to base my decision on the flags of the windows, I can just put a hash naming the "special" windows in my perl module, and just update it as I encounter new "problem" applications. -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
