You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 14, 2024. It is now read-only.
What steps will reproduce the problem?
1. It's not a problem - rather an enhancement request
2. The /root/.config/Ostinato.conf file stores the Ostinato Window positions -
but it's not easy to reset if you've messed up the configuration.
I ran into an issue where the entire lower half of the Ostinato screen was
completely gone (no port stats, counters...etc). I'm assuming it was an
in-advertent window resize (maybe I released the button at the wrong time?) -
resulting in the bottom section being completely gone. Since there was no
bottom section visable, I wasn't able to "pull" it back up to a visible size.
I tried all sorts of screen resizes, but could never get the display back.
I tried to re-install, but it looks like the "ostinato.conf" file doesn't get
uninstalled when I removed Ostinato - so the re-installed version had the same
missing screen.
To fix the issue, I discovered the /root/.config/Ostinato.conf file and removed
it. Then, when I started Ostinato, it defaulted to a standard display.
If there was a "Set to Defaults" or "Reset Screen" menu option, that would have
been a handy way to restore the screen display without having to remove the
file.
It's not a big deal - now that I know about the Ostinato.conf file - but I
figure it's a fairly simple thing to implement too.
What version and revision of the product are you using (available in the
About dialog)? I had this issue on version 0.3, but it also applied to version
0.5 (which I upgraded the system to, but corrupted screen position was still
there.
On what operating system? Opensuse 11.3 64bit
Please provide any additional information below.
Original issue reported on code.google.com by [email protected] on 27 Mar 2012 at 8:39
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 27 Mar 2012 at 8:39The text was updated successfully, but these errors were encountered: