Closed GoogleCodeExporter closed 9 years ago
This is a misunderstanding of the CTRL+O function. CTRL+O opens a document and
not
the project. Therefore you have to be in a project to open a document.
If you go to the File menu and click Close (not Close Project) the Main window
appears without a document. Press CTRL+O and Adapt It opens the Start Working
dialog
with the list of current documents for the project.
Documents exist within projects, therefore Adapt It cannot respond to CTRL+O if
no
project is open. It doesn't know where to look.
Original comment by bussa5...@gmail.com
on 12 Mar 2009 at 4:47
Use CTRL+W to open a project if none is open.
Original comment by bussa5...@gmail.com
on 12 Mar 2009 at 4:50
Original comment by bussa5...@gmail.com
on 12 Mar 2009 at 5:07
Thanks for this explanation of Ctrl+O.
Yes I mixed the concepts of projects and documents in the description of the
issue 35
above.
Looking again into AI/File/Close it is not specified, what is closes (document
or
project?)
Looking how Menu/File is built up:
- the first block with 9 options (New ... Unpack Document) are all for documents
- the 3rd block with 3 options (Start working ... Change folder) is for
projects.
So the close option seems to close a document, (not a project) and supposingly
leaves
the actual project open.
Testing this issue again, here is what I find:
- A project with a document is open,
- Choose the close option by File/Close
- Trying to use the open option Ctrl+O does not work
- On the other hand, File/Open works and
-- shows the same project (which has been loaded before) and
-- gives the choices of documents already worked with in this project.
-> If a document in a project is closed, let the Ctrl+O and File/Open work in
the
same way, this is to give the choice of documents to be loaded in the project
which
was active before the close option was activated.
Original comment by wolfgang...@gmx.de
on 13 Mar 2009 at 7:14
The behavior you expect happens on the Windows and Mac versions, but not on the
Linux
version for some reason (yet to be determined). I see that there also is a
conflict
in the hot key assignments for the Linux version's File menu. Ctrl+W shows as
the hot
key for two different commands. It should only appear for the Start Working...
command. I'm not sure yet how the Ctrl+W hot key also gets assigned to File |
Close
command in the Linux version. We have not made that hotkey assignment in the
programming code itself. Perhaps the Window manager in Ubuntu (Gnome) tries to
make
that assignment automatically, I'll have to research it further. Therefore, I'm
leaving this issue open, marking its status as "Accepted" and I will try to
find a
solution for the next update.
Original comment by adaptitbill@gmail.com
on 13 Mar 2009 at 11:28
OK, I investigated, and found out that the GTK toolset (which Ubuntu uses)
automatically assigns Ctrl+W as their standard hotkey for closing a file/window
(compare other Linux applications such as gEdit, kWrite, and the Gimp which
also use
Ctrl+W to close a file/window). Therefore, I've made the Linux version follow
the Mac
version in using the Ctrl+Shift+O [oh] as the hotkey for invoking the Start
Working... wizard. This allows the Ctrl+W key to work correctly for File |
Close, and
Ctrl+0 to work correctly for File | Open (both actually open the wizard, but the
effect is different depending if the project was also closed or not. If the
project
is closed both Ctrl+O and Ctrl+Shift+O open the Start Working wizard at the
Project
page/dialog. If the Project is already open, these hotkeys both invoke the Start
Working wizard at the Document page/dialog. The original assignments of Ctrl+W
for
the Start Working wizard, and Ctrl+O for opening a document (when project is
open)
remain as they were in the Windows version. These changes for the Linux version
will
be in the next update 4.1.2.
Original comment by adaptitbill@gmail.com
on 14 Mar 2009 at 1:50
Original issue reported on code.google.com by
wolfgang...@gmx.de
on 12 Mar 2009 at 11:07