vtwm iconmanager bug with konqueror - Xwindows

This is a discussion on vtwm iconmanager bug with konqueror - Xwindows ; Hi Why vtwm iconmanager reads the icon name of konqueror only once (i.e. don't update it)? By the way, such nuisance occurs with opera browser too -Templar-...

+ Reply to Thread
Results 1 to 4 of 4

Thread: vtwm iconmanager bug with konqueror

  1. vtwm iconmanager bug with konqueror

    Hi

    Why vtwm iconmanager reads the icon name of konqueror only once (i.e.
    don't update it)?

    By the way, such nuisance occurs with opera browser too

    -Templar-

  2. Re: vtwm iconmanager bug with konqueror

    In article ,
    sword@bonbon.net (Templar) writes:
    >
    > Why vtwm iconmanager reads the icon name of konqueror only once (i.e.
    > don't update it)?


    Not knowing the code of konqueror, I can only suggest three reasons:
    - It only tells the WM once (unlikely). I'll discount this entirely.
    - It tells the WM in a way the WM doesn't understand. If konqueror
    doesn't follow the guidelines as mentioned in the ICCCM
    (specifically, using functions XSetIconName(), XSetWMIconName(),
    or XStoreName(), which set either the WM_ICON_NAME or WM_NAME
    properties), then yes, VTWM won't see the changes.
    - It's buggy. Sure, why not? Could be.

    Knowing the code of VTWM, I can only suggest one reason:
    - It's buggy. Yes, it's certainly possible VTWM has bugs regarding
    this, but I run many apps that change their icon name, and VTWM
    does pick up on the changes (Mozilla, xv, asmail, xfig, etc., all
    of which use different toolkits/libraries).

    What version of VTWM are you using? What version of konqueror? Have you
    notified the maintainers of konqueror about this?

    Dave
    (VTWM maintainer)

    --

    A: Because it messes up the order in which people normally read text.
    Q: Why is top-posting such a bad thing?
    A: Top-posting.
    Q: What is the most annoying thing on usenet?


  3. Re: vtwm iconmanager bug with konqueror

    hawkeyd@visi.com (D J Hawkey Jr) wrote in message news:<40eee87e$0$4751$a1866201@newsreader.visi.com>...
    > In article ,
    > sword@bonbon.net (Templar) writes:
    > >
    > > Why vtwm iconmanager reads the icon name of konqueror only once (i.e.
    > > don't update it)?

    >
    > Not knowing the code of konqueror, I can only suggest three reasons:
    > - It only tells the WM once (unlikely). I'll discount this entirely.
    > - It tells the WM in a way the WM doesn't understand. If konqueror
    > doesn't follow the guidelines as mentioned in the ICCCM
    > (specifically, using functions XSetIconName(), XSetWMIconName(),
    > or XStoreName(), which set either the WM_ICON_NAME or WM_NAME
    > properties), then yes, VTWM won't see the changes.
    > - It's buggy. Sure, why not? Could be.
    >
    > Knowing the code of VTWM, I can only suggest one reason:
    > - It's buggy. Yes, it's certainly possible VTWM has bugs regarding
    > this, but I run many apps that change their icon name, and VTWM
    > does pick up on the changes (Mozilla, xv, asmail, xfig, etc., all
    > of which use different toolkits/libraries).
    >
    > What version of VTWM are you using?

    vtwm-5.4.7-20031103

    > What version of konqueror?

    from KDE 3.2.3

    > Have you notified the maintainers of konqueror about this?

    not yet, but I've tested konqueror on AfterStep-2.00.beta4b
    and its WinList2 absolutely normaly updates the notorious WM_ICON_NAME

  4. Re: vtwm iconmanager bug with konqueror

    In article ,
    sword@bonbon.net (Templar) writes:
    > hawkeyd@visi.com (D J Hawkey Jr) wrote in message news:<40eee87e$0$4751$a1866201@newsreader.visi.com>...
    >> In article ,
    >> sword@bonbon.net (Templar) writes:
    >> >
    >> > Why vtwm iconmanager reads the icon name of konqueror only once (i.e.
    >> > don't update it)?

    >>
    >> [SNIP]
    >>
    >> What version of VTWM are you using?

    > vtwm-5.4.7-20031103
    >
    >> What version of konqueror?

    > from KDE 3.2.3
    >
    >> Have you notified the maintainers of konqueror about this?

    > not yet, but I've tested konqueror on AfterStep-2.00.beta4b
    > and its WinList2 absolutely normaly updates the notorious WM_ICON_NAME


    OK, I'll try to make some time to look into this; it'll be a week or two
    at a minimum.

    Shoot me a mail with your preferred e-mail addy; we can take further
    discussion off-list. The "From" of this message is my e-mail addy.

    Thanks,
    Dave

    --

    A: Because it messes up the order in which people normally read text.
    Q: Why is top-posting such a bad thing?
    A: Top-posting.
    Q: What is the most annoying thing on usenet?


+ Reply to Thread