On 4/19/12 08:41 , "Steiner, Mathias" <email@example.com> wrote:
>When using CSS on my netbook, there is 'wasted' space at the very bottom
>of the display, what used to be called the "status bar" in Firefox... is
>there any way to get rid of that?
>Alternatively, is there a way to edit/rearrange the area?
>Unless a window is full screen, I get double height, since the 'status
>bar' wraps, even though it isn't crowded. H
>ere's a screen shot:
Within a BOY display you can enable/disable that "Status Bar" at the
bottom of the display by switching to "compact mode".
Use the context menu of the BOY display (right mouse button) or press F8.
In general, the makeup of your "product" decides these things.
You could create a version of CSS for your site that does not have a
"Status Bar" at all.
So far, however, I think all sites decided to include the status bar.
Still, you can then decide if you want that memory display that's shown in
or not, which would also influence how soon your status bar doubles its
height as the window becomes more narrow.
The SNS product for example does not include the status bar mem display.
I assume it would be a good idea to add a global "status bar on/off"
toggle to every CSS product, instead of only offering that option from BOY
But this is one of the many little details where each site has different
requirements, which results in different "products":
* Initial "Log In" dialog or not?
* Initial "Workspace" selection or not?
* Status bar or not?
* Toolbar or not?
* Include SDS or BOY?
* Include access to Channel Archiver, RDB-based archive, AAPI, ...?
* Include most things that users at your site need, or offer empty shell
and let users install exactly what they want?
* Create a default project like "CSS" in the workspace so that users can
right away save files there, or leave it to each user to create their own
projects with more meaningful names as needed?
Creating a site-specific product has become easier over the years. It can
be done with zero Java code, "only" configuration as described in
Still, it's likely to take days, not hours.
On the agenda for future CSS development we do list once more to
simplify/unify the CSS product generation,
http://sourceforge.net/apps/trac/cs-studio/wiki/Release3.2.0 , so we'll
- Navigate by Date:
Problem in porting EPICS on microblaze softcore processor ssahoo
RE: Problem in porting EPICS on microblaze softcore processor Dalesio, Leo
- Navigate by Thread:
RE: Problem in porting EPICS on microblaze softcore processor Hill, Jeffrey O
SRS PTC10 support? Pete R. Jemian