I'd do it something like this: - a new resource flag: "Remember state" (something like that) - a B_LOAD_STATE app launch message - a B_SAVE_STATE shutdown message (probably a B_QUIT_REQUESTED with a "save_state" field) The resource flag would keep non-state-aware apps out of the loop The load/save messages would put the actual state-management in the hands of the application. (different apps - different ways of saving state) All backwards-compatible with Be's R5. /Jonas Sundstrom. ~ www.kirilla.com ~ www.kioki.com