A temporary fix is probably to have a shortcut that calls a script
that does the same changes to the xml file that you edited after
checking to make sure that bibledit is not running.
On 11-02-02 01:08 AM, Paul-Jennifer_Schaefer wrote:
Neil,
Holding Alt and dragging the window does not work for
"subwindows."
Regardless of where you put the mouse pointer within the program
window, it only drags the main window (the whole program) around
the computer screen. It will not move a "subwindow" around within
the main program window. I have tried this and many other
variations to move a "subwindow," but this has no effect (don't
know if "subwindow" is the right term--I mean within Bibledit you
have a pane in which you edit, and optional other panes which give
references, etc. if you display them--these are what I am calling
"subwindows").
These panes (or subwindows?) can be moved independently within the
main program window: they each have their own "title bar" which
can unfortunately be "grabbed" by the mouse pointer and dragged
"up" and *behind* the main Bibledit toolbar at the top. If you do
this and then "let go" of the subwindow's title bar while the
title bar is not visible, there appears to be no way to get the
subwindow back to its original place apart from editing the
configuration file, which is not practical for ordinary users. As
such this problem is something which needs to be changed in
Bibledit.
Tues has also suggested that if the screen resolution were
changed, that would force the subwindows to resize. I haven't
tried this, but again this is not practical for "ordinary" users.
(While this is my first experience with Linux, I do have fairly
extensive computer proficiency. I have been actively using
Bibledit 4.0, from the Lucid BALSA distribution, for less than a
week.)
Paul Schaefer
Ghana
On 2/2/2011 4:59 AM, Neil Mayhew wrote:
Hi Paul,
Another possibility is to hold down Alt and drag the window.
This has the same effect as dragging the title bar, but can be
done by clicking in any part of the window.
It's possible this has been set to a different key combination
on your system, but on a stock Balsa system it's Alt-Button1.
--Neil
On 2011-02-01 04:35, Paul-Jennifer_Schaefer wrote:
Alexander Vinokurov's solution below:
------ Original Message --------
Paul,
I found out how to restore the position. Open in any text editor the following file:
~/.bibledit/configuration/configuration.1.xml (here the tilde stands for your home directory; you can type the name of your text editor and then that path. For example, in Ubuntu with its 'gedit' text editor it will be like this:
gedit ~/.bibledit/configuration/configuration.1.xml)
Then search for (in gedit you press CTR+F) the line 'window-y-positions' (without quotes and make sure the 'positions' is plural because there is another instance of 'window-y-position' which does something different). You will get something like this:
<window-y-positions>
<value>0</value>
<value>-17</value>
<value>0</value>
</window-y-positions>
Change the middle value into '0' (zero) and save the file. If your text editor can show line numbers it should be the line 101. At least it is so in my case. Here I put '-17' but you may have another value. But minus means that the titlebar is too high and perhaps hidden. If you have positive value it means that the bar is too low. So zero is just on.
I assume that Bibledit is off when doing that.
On 2/1/2011 11:31 AM, Kim Blewett wrote:
Hi
Paul,
I did this too on Bibledit, a year ago; I'm trying to
remember what I did to solve it. It still is a problem in
BE-GTK v 4.1; I've just got myself into the same bind.
Here's one suggestion: Copy your hidden project to a new
project (File - Project - Copy to). Then you can delete the
original, hidden project.
I agree that this is a problem that needs a solution! I'm
copying the bibledit newsgroup on this message; any other
ideas out there?
Kim
On 01/02/11 20:35, Paul-Jennifer_Schaefer wrote:
Lucid on EEEpc, Balsa is good but
working under Linux has a lot of hidden challenges because
it is so different from Windows (in the nuts-and-bolts).
My main problem at present is that I have moved the
subwindow in Bibledit (the one where you type in
scripture) so that its title bar is hidden underneath the
general toolbar of Bibledit, and there appears to be no
way to get the title bar back down. Since the subwindow
also moved to the left when this happened, I cannot see
the first several cm of text on each line. Thus I am
effectively prevented from using Bibledit at all.
(Someone who also uses Bibledit though not BALSA has given
me a technical solution which involves editing some kind
of control file. I'm sure I can follow the directions,
but this would not be a reasonable option for the target
BALSA user.)
|