OOOOOOOOOOOoops. Display changed somehow.

  • Anonymous - 2012-06-13

    There I was browsing through my feeds this morning with the headline pane on
    the top, the feed on the bottom and the reading pane on the left when all of a
    sudden, I pressed some key or combination of keys and almost everything
    changed. My headline pane disappeared, the feed pane appeared at the top with
    a tab which I couldn't close.

    I found the headline pane at the bottom of the page and was able to raise it
    up some, but I still can't get back to the configuration I had before.

    Can anyone be of any help to me on this? I have been using this for years and
    haven't had quite this problem before.

    Thanks, probably,


  • Torsten Rendelmann

    Hi Bob,

    depending on the version of Bandit you use, you may find a file
    ".settings2.xml" in your local
    "C:\Users\<YOUR_WIN_USERNAME>\AppData\Roaming\RssBandit" path.
    This file contains the UI widget settings (form positions, layout, sizes,...).
    To get around the display issue, please rename/delete this file, then start
    the application again.

  • Anonymous - 2012-06-14

    Yes, t_rendelmann, I do find the file .settings2.xml, although not
    quite where you thought. I followed your suggestion and, first, deleted the
    file, then renamed it. In both cases, the file was recreated when RSS Bandit
    was restarted. I suppose this might mean that .settings.xml might be corrupt,
    but I'm not sure. I can, of course use the program the way it is, but
    everything is now upside down. LOL.

    Any other ideas, or anyone?



  • Torsten Rendelmann

    No, there is no .settings.xml missing or destroyed: the "2" means .NET
    framework version "2". Re-creation of the file is intended. Does your initial
    issue still exists?

  • Anonymous - 2012-06-15

    This morning, I decided to just make a copy of the .settings.xml file and
    rename that file as .settings2.xml. Whatever the reason, I now have my old
    display back. I sure wish I knew which key or key combination I hit to screw
    up the display before so I could try to avoid it from now on.

    Anyway, I'm back to my normal.

    Thanks everyone.



Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks