Dear all.
Is there any way to open a new window but keeping the original window
without any change at all? When I open a new small window in the
center, the original window changes to "non-maximize" status and it is
not possible to keep this window maximized and the new small windows in
the center at the same time. If I try to maximize again the original
window, the new small window disapears because it keeps behind the
original one.
Thanks.
Jokin

In article <1134417695.928900.78680 (AT) g14g2000cwa (DOT) googlegroups.com>,
joaquin.castilla (AT) gmail (DOT) com says...
No.

The nature of a "Maximized window" is that there is just *One Window*
that has been Maximized. If you want to open a second window, then
either:

a) The second window is maximized, and the first is invisible.

b) Neither window is maximized.

The obvious workaround, if you want mutliple windows visible - is not to
run with the windows maximized ever, just make the windows you want
maximized as big as possible in non-maximized mode.

Its not a limitation of filemaker, per se, its how Windows works.
Filemaker is a Windows MDI application (Multiple Document Interface"),
which has a 'Main Window' and then multiple child 'document' windows
within it. If a child window is maximized then it ceases to have its own
border and shares its border with the parent window. If its not in
maximized mode then the child windows can be dragged around, resized,
and layered in the parent window space, each with its own title bar, and
border.

This is how all applications with multiple document windows (email
clients, word processors, etc) used to be written ... lately MDI has
fallen out of favour and most new applications spawn completely separate
processes for each document window (so you'll actually see them as
separate tasks in task manager).

This "more modern" way has the advantage that its freed from the
limitations of the MDI approach, but it uses more computer resources
(CPU & RAM) to run all these tasks searately -- MDI was invented a long
time back, when 8 MB of RAM was pretty impretty impresses.

FWIW I think FM should abandon MDI, but until it happens we are stuck
with its limitations (and benefits).

-cheers,
dave

I'm with you Dave. It would have the happy side-effect of making the
interface a lot more like the Mac version.

Probably won't happen anytime soon, as FileMaker likes to present modal
dialogs. Going away from MDI would mean that you could be entering data into
a table while you're defining fields for the same.

Bill


"42" <nospam (AT) nospam (DOT) com> wrote

Jokin wrote:

Make your main window one pixel smaller than maximized in either height
or width. This allows you to open other windws, and this one will
remain the same size.

You could mess with specific window sizes, but this following simple
script will accommodate any monitor. Note that all we're doing is
setting height to current (maximized) height -1:

Adjust Window
[ Maximize ]
Move/Resize Window
[ Current Window; Height: Get ( WindowHeight ) - 1 ; Width: Get (
WindowWidth ); Top: Get ( WindowTop ); Left: Get ( WindowLeft ) ]

Matt

In article <avadnWVaUs4_jwPenZ2dnUVZ_tSdnZ2d (AT) giganews (DOT) com>, wjm (AT) wjm (DOT) org
says...
The Client-Server arrangement already solves most of those problems, and
could easily be extended to a local multi-process solution.

The only problem that remains is that unlike a word processor, fm
document windows do need awareness of eachother to run scripts, for
application modal dialog boxes and so on, so some sort of master
process/child process interprocess communication structure has to be in
place... essentially recreating MDI without using the MDI API.

A bit of work for sure, but not as big a deal as you might thing.
Especially if you set up the master process as a 'local fm server', that
ran all the scripts etc, and the child processes were just 'viewers'...

-