On Wed, Mar 21, 2012 at 2:08 PM, Igor Stasenko siguc...@gmail.com wrote:
On 21 March 2012 15:25, Guillermo Polito guillermopol...@gmail.com
wrote:
So, If I have an image with no GUI, which UIManager should I install,
how
and when? Because at image startup I can't use a MorphicUIManager
we should add that to the class comment.
and method comment.
can somebody open a ticket?
Stef
On Mar 21, 2012, at 5:07 AM, Igor Stasenko wrote:
the logic there was to set a non-interactive ui manager
for headless sessions only , and then restore back a previous one
(whatever it is), once
indeed the non-interactive one keeps the previous version alive in the
instvar...
I just copied the existing implementation (without much motivation).
Bit for simplicity's sake we should simply instantiate every time the proper ui
manager, that would simplify these ugly methods quite a bit.
So, If I have an image with no GUI, which UIManager should I install, how
and when? Because at image startup I can't use a MorphicUIManager if I
don't have it loaded into the image :).
On Wed, Mar 21, 2012 at 8:00 AM, Camillo Bruni camillobr...@gmail.comwrote:
indeed the non-interactive one
On 21 March 2012 15:25, Guillermo Polito guillermopol...@gmail.com wrote:
So, If I have an image with no GUI, which UIManager should I install, how
and when? Because at image startup I can't use a MorphicUIManager if I
don't have it loaded into the image :).
Commanline ui manager? or just
Hi,
I was doing some hacking, and playing with NonInteractiveUIManager. And it
puzzled me that I realized that it has an inst var *uiManager* that seems
to refer to an uiManager it's replacing.
But my UIManager is not replacing anyone, it's my default and unique
UIManager and this var points to
the logic there was to set a non-interactive ui manager
for headless sessions only , and then restore back a previous one
(whatever it is), once session is changed back to headfull.
if its uiManager is nil, it should reset the default manager,
if i remember correctly, then UImanager itself will
the logic there was to set a non-interactive ui manager
for headless sessions only , and then restore back a previous one
(whatever it is), once session is changed back to headfull.
if its uiManager is nil, it should reset the default manager,
if i remember correctly, then UImanager itself will
