[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Freezing frameset-restore
From: |
martin rudalics |
Subject: |
Re: Freezing frameset-restore |
Date: |
Thu, 06 Mar 2014 18:27:18 +0100 |
> CLEANUP allows to \"clean up\" the frame list after restoring a frameset:
> :delete Delete all frames that weren't restored. This is the default.
Why the term "restored" here and not "reused"?
> :keep Keep all frames.
> FUNC A function called with two arguments:
> - FRAME, a live frame.
> - ACTION, which can be one of
> :rejected Frame existed, but was not a candidate for reuse.
> :ignored Frame existed, was a candidate, but wasn't reused.
> :reused Frame existed, was a candidate, and restored upon.
> :created Frame didn't exist, was created and restored upon.
IIUC "cleanup" means to take care of frames that were not "reused". I
understand that we should take care of "rejected" or "ignored" frames.
But why care about "reused" and "created" ones?
martin
- Freezing frameset-restore, Juanma Barranquero, 2014/03/05
- Re: Freezing frameset-restore,
martin rudalics <=
- Re: Freezing frameset-restore, Juanma Barranquero, 2014/03/06
- Re: Freezing frameset-restore, martin rudalics, 2014/03/06
- Re: Freezing frameset-restore, Juanma Barranquero, 2014/03/06
- Re: Freezing frameset-restore, Juanma Barranquero, 2014/03/06
- Re: Freezing frameset-restore, martin rudalics, 2014/03/07
- Re: Freezing frameset-restore, Juanma Barranquero, 2014/03/07
- Re: Freezing frameset-restore, martin rudalics, 2014/03/07
Re: Freezing frameset-restore, Stefan Monnier, 2014/03/07