Menu
▾
▴
#31 Restore match window when the main window is restored
If you switch to another application, you have to restore
the translation window and the match and glossary
window separately. It would be cool, if the match and
glossary window were restored automatically when the
translation window is restored.
Logged In: YES
user_id=488500
OK, It's a nice request.
However I plan to rewrite OmegaT windowing system, so I'd
schedule it for future.
Logged In: YES
user_id=488500
I plan to make OmegaT consist of a single window,
with resizable components:
- main translation window
- matches window
- glossary window
Logged In: YES
user_id=488500
inserted into 1.5 schedule, see roadmap:
http://sf.net/docman/display_doc.php?docid=25106&group_id=68187
(1.4.6 was cancelled)
Logged In: YES
user_id=168045
I enjoy the two-window system we currently have. I don't find it annoying that the two windows are seperate. I can understand that an option to bring both windows to the front in one action would be handy, but having two windows is not annoying to me. In fact, it enables me to close the one window and still use OmegaT (for example, when I don't want to use only match propagation, and not fuzzy matching).
So... I suggest you keep it as two (or more) windows, but have the option to bring both windows to the front at once. You can do this by either having the main window check to see if all other windows are "in front", or by having a third window which, if brought to the front, automatically brings the other windows to the front as well. The third-window option allows the user to choose whether he wants to have all windows brought to the front or not, because if he doesn't, then he simply only clicks the windows that he wants and not the third window. Am I making sense?
Logged In: YES
user_id=488500
Hi Samuel,
If there will be a possibility to close (and later open) a
match & glossary subwindow inside a single one, will it make
any difference for you?
Logged In: YES
user_id=488500
The main window class will be refactored a bit for 1.4.6.
It doesn't mean this RFE gets implemented for sure, but I'll
try...
Logged In: YES
user_id=488500
Implemented in 1.4.6 beta 4
(to be published near the end of the week)
Logged In: YES
user_id=488500
Will never be fixed, due to problems that come out of it,
the fix currently in 1.4.6 beta 4 will be reverted back.
Logged In: NO
Ok. thank you :)
JC