text object, message, and comment, when edited are reinstantiated and thrown on top of the glist stack

text object, message, and comment, when edited, are reinstantiated and thrown on top of the glist stack which messes with the preset hub instances that rely on externally saved presets and which rely on prerecorded node locations. This renders saved presets useless. May also need to warn users that to front/to back commands may exacerbate this problem for all objects. May need to be addressed through both retaining the existing object position and improving the hub logic.