3 simple questions

HiI have a frameset with 2 frames

left and right

left is always the same page with few buttons and right is form/view/page etc (depands what u choose in left page).

I have form - “form1” with some fields and cancel button : Command([FileCloseWindow]).

And when i click it its closing whole database and goe to workspace.What should I do to close only this form and return to framset with for ex some view ?

And second question:

I have outline:

With 2 fields

-some view

-some form

When i created a field with view its automaticly made a view small icon , but when I created a field with form it doesnt create any icon.(icon is shown in designer but not shown i Notes)

The last one:

It is possible to make text on page which is computed ? for ex. @name([CN] ; @userName)

Thx

Subject: 3 simple questions

The simple answer to the first problem is that you should never open forms/documents into a frameset in the Notes client – let them open into their own windows. Experienced users will use the Enter/Return key from a view to open a document, and then use Esc to close/save their documents. If forms/documents open into framesets, then they will close the database, not just the document. Forcing the users to work any other way is just making their lives difficult for no good reason.

For the third, look at Create → Computed Text.

As to the second, I’m afraid I never use the default outline, so I can’t say how its supposed to work.

Subject: RE: 3 simple questions

I agree that the ESC key cause a problem in Framesets, but if I adhere to this logic, what is the use of having Framesets in the Notes Client at all?

Subject: Navigation and wot-not

They’re fine for setting up something like an embedded outline to the left of the screen, and a view to thr right. However, I never have documents or forms open into these specific frames – that’s what Stan is getting at I think.

Subject: RE: Navigation and wot-not

I still think that it just negates the need for Framesets at all in the Notes Client. Yes the ESC key can be problematic, but once I got around the SetTargetFrame bugs in Notes, as well as problems creating response documents, I found I preferred it to opening a doc on its own, especially when users opened a document through a doclink and you want them to have an application context.

Subject: RE: Navigation and wot-not

Well, if you think that negates the need for framesets, then that’s your prerogative.

You asked why use them at all if you’re not opening a document within the frameset. I’m just saying they have a use in defining the Notes client UI for many of my apps, but that’s as far as I go with them. I don’t like opening documents within frames, and find framesets a burden (keep in mind that at work we’re still coding to a base version of 5.05, and as we know there are many frameset-related bugs there).

Returning to the need for framesets, of course I could use the “old” navigator and view method, but I find navigators a royal pain in the @rse, and they’re effectively “deprecated” now in any case.

Subject: RE: Navigation and wot-not

Just couple 2 or 3 or 4 Frameset Bugs yes:-), but s I said, once I worked around them I was a happy camper.

Yes wall all have our preferences and while I despise FrameSets on the web client, I have found them very useful in the Notes Client.