FVWM: fvwm showing kill icon when starting and restarting

[lee]

Hi,

what could be the reason for fvwm showing its kill icon on startup and
when restarting?

It seems to do that since after I made some change to the configuration,
and I don't remember what that change was.  When it first happened, I
thought "ok, it's been restarted like so often and might be confused and
this will go away on a fresh start" --- but it didn't.

The configuration is here: https://github.com/lee-/fvwm


-- 
Again we must be afraid of speaking of daemons for fear that daemons
might swallow us.  Finally, this fear has become reasonable.

Re: FVWM: fvwm showing kill icon when starting and restarting

[Dan Espen]

lee  writes:

> Hi,
>
> what could be the reason for fvwm showing its kill icon on startup and
> when restarting?

Do you mean kill cursor?

> It seems to do that since after I made some change to the configuration,
> and I don't remember what that change was.  When it first happened, I
> thought "ok, it's been restarted like so often and might be confused and
> this will go away on a fresh start" --- but it didn't.
>
> The configuration is here: https://github.com/lee-/fvwm

Somewhere in there you're issuing a Delete or Destroy not in a window
context.

-- 
Dan Espen

Re: FVWM: Is there a way to ignore other windows when placing one?

[lee]

Michael Großer  writes:

> Michael Großer wrote:
>> Dan Espen wrote:
>>> lee  writes:
>>> 
 Hi,

 the subject pretty much says it:

 Can I somehow make it so that fvwm ignores particular windows when
 figuring out where to place a new one?
>>> 
>>> Not that I know of.
>>> 
>>> What are you trying to do?
>> 
>> Without awaiting the answer about what is tried to do:
>> 
>> If no official way helps, there is always a dirty but "creative"
>> approach.
>> 
>> - Minimize the particular windows that you want to ignore
>> - Hide their icons
>> - Place your new window
>> - Unhide the hidden icons
>> - Reopen the minimized windows
>> 
>> The process would perhaps have an optical effect that is not so good
>> looking, but the "creative" approach could solve your problem if no other
>> expert delivers a better solution :-)
>
> Another idea:
>
> - Move the particular windows to a desktop that solely exists for that purpose
> - Place your new window
> - Move the cleared away windows back to their original place

Thanks, these are good ideas :)

I haven't figured out how to use multiple desks, though.  I tried that
once and apparently got multiple desks just by naming some, but no way
to switch between them.


What I'm trying to do is achieving more reasonable window placement.  I
found that one small window can make it so that a larger window is not
placed the way I would consider reasonable.  I found that out by
manually moving the small window around to see what placement I would
get and concluded that if fvwm would ignore the small window when it
figures out the placement of the larger one, the larger window would be
placed well.  So I wondered if I could have fvwm ignore the small
window.

Now you suggest to move the small window out of the way automatically
rather than manually --- something I haven't thought of :)


Is there some way to make it so that a function which moves the small
window out of the way is always called when fvwm is about to figure out
where to place a window?  And how do I prevent this function from being
called when the window that is moved out of the way is placed?

(In most cases, I probably won't need that because I'm using starter
functions to start applications which create windows, but applications
can create windows by themselves ...)


-- 
Again we must be afraid of speaking of daemons for fear that daemons
might swallow us.  Finally, this fear has become reasonable.

Re: FVWM: Is there a way to ignore other windows when placing one?

[Dan Espen]

elliot s  writes:

> If fvwm can (be made to) optionally ignore lower layers during
> auto-placement, that would work.

Long ago, Fvwm got so many options that I'm unable to keep track.

MinOverlapPlacementPenalties has a series of arguments including "below"
that may help.

-- 
Dan Espen

Re: SOLVED: Re: FVWM: fvwm showing kill icon when starting and restarting

[Dan Espen]

lee  writes:

> Dan Espen  writes:
>
>> lee  writes:
>>
>>> Hi,
>>>
>>> what could be the reason for fvwm showing its kill icon on startup and
>>> when restarting?
>>
>> Do you mean kill cursor?
>
> I guess so --- it's some icon which is probably supposed to look like a
> skull with bones under it.  I vaguely remember having seen that
> somewhere many years ago, and this icon reminds me of it.
>
>>> It seems to do that since after I made some change to the configuration,
>>> and I don't remember what that change was.  When it first happened, I
>>> thought "ok, it's been restarted like so often and might be confused and
>>> this will go away on a fresh start" --- but it didn't.
>>>
>>> The configuration is here: https://github.com/lee-/fvwm
>>
>> Somewhere in there you're issuing a Delete or Destroy not in a window
>> context.
>
> "not in a window context"?  I'm only destroying functions ... Oh, I
> found it!  I used "Destroy" where I should have put "DestroyFunc".

Glad to hear.

I think you have "not in a window context" figured out.

A title bar button has a window context, a destroy on a window button
"knows" which window to destroy.

A root window key binding for destroy doesn't know which window to
destroy (there is no window context), so fvwm changes the mouse pointer
to the skull you saw waiting for a click on a window to know which
window to destroy.

-- 
Dan Espen

SOLVED: Re: FVWM: fvwm showing kill icon when starting and restarting

[lee]

Dan Espen  writes:

> lee  writes:
>
>> Hi,
>>
>> what could be the reason for fvwm showing its kill icon on startup and
>> when restarting?
>
> Do you mean kill cursor?

I guess so --- it's some icon which is probably supposed to look like a
skull with bones under it.  I vaguely remember having seen that
somewhere many years ago, and this icon reminds me of it.

>> It seems to do that since after I made some change to the configuration,
>> and I don't remember what that change was.  When it first happened, I
>> thought "ok, it's been restarted like so often and might be confused and
>> this will go away on a fresh start" --- but it didn't.
>>
>> The configuration is here: https://github.com/lee-/fvwm
>
> Somewhere in there you're issuing a Delete or Destroy not in a window
> context.

"not in a window context"?  I'm only destroying functions ... Oh, I
found it!  I used "Destroy" where I should have put "DestroyFunc".

Thanks!


-- 
Again we must be afraid of speaking of daemons for fear that daemons
might swallow us.  Finally, this fear has become reasonable.