>>>>> fergal_at_ilo.dec.com writes:
> However I ran into a problem... While I could start a Menu
> afresh (i.e. implemented a function NewMenu which destroys the old
> instance first) there was now way to implement a NewFunc, which
> resulted in all my functions being doubled up...
I think I recall someone once posting that DestroyMenu was supposed to
work on Functions too. Then again I don't bother destroying anything
so it's not an issue for me :-)
> So why isn't there a corresponding DestroyFunc command?
If I'm correct in my guess above then DestroyMenu should be aliased to
DestroyFunc.
> And infact it would make sense (or it seems so to me) that this
> should exist and it maintains the orthogonality of the command
> syntax? Things that are created can be destroyed. On a similar
Agreed.
> note, orthogonality would suggest that perhaps KillModule should be
> DestroyModule?
I disagree. Running a module involves starting a separate process.
On most, if not all, of the platforms that fvwm runs, the removal of
that process is referred to as killing. Killmodule fits. Menus and
functions are objects native to the fvwm process. Destroy fits there.
Dave Goldberg
Post: The Mitre Corporation\MS B305\202 Burlington Rd.\Bedford, MA 01730
Phone: 617-271-3887
Email: dsg_at_mitre.org
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Mon Mar 25 1996 - 15:58:38 GMT