I am looking at converting from AREV to OI.

My existing system uses mostly collector windows called from a subroutine with the processing etc within the SR.

The collector windows have popups etc to aid the user in entering the data correctly.

I do not seem to be able to replicate this functionality in OI !!

I must be missing something.

I created a form with bo table association, then put on an edit box.

I attached a quick event to this box on the Option event, to perform a popup, but i cannot get it to work.

It must be something simple,like me, but what.

Similarly how can I execute a form(window) within a procedure,and are all the variables for that form available.

Any help greatly apreciated.

Mike,

The collector windows have popups etc to aid the user in entering the data correctly. I do not seem to be able to replicate this functionality in OI !! I must be missing something. I created a form with bo table association, then put on an edit box. I attached a quick event to this box on the Option event, to perform a popup, but i cannot get it to work.

Doesn't your popup appear?

Or does it appear but returns no value in the edit box?

(Btw - why an edit box and not an edit line? Normally you get short values from a popup.)

Similarly how can I execute a form(window) within a procedure,and are all the variables for that form available.

See e.g Aaron's or Dsig's replies to http://www.revelation.com/WEBSITE/DISCUSS.NSF/f12696d31000b22a8525652b00831bb2/b0b0ebba33241d58852564b50074a50f?OpenDocument.

- Oystein -

Oystein, thanks for replying.

An edit box against an edit line, no reason just experimenting.

I get nothing returned from the POPUP.

Mike

Mike,

I think we have having communication problems with terminology.

When you say "nothing is returned from the Popup", did you surmise this from viewing the return value from the debugger? When you first created the popup in the UI Workspace, did you test it and did it return a value during the test mode in the UI Workspace?

Tom

Mike,

If the popup really returns something when you test it from UI Workspace - check your edit box's quickevent settings:

Event: OPTIONS

QuickEvent Options: Execute a popup

Send Message to: Entity

*POPUP**

Message: EXECUTE (greyed out)

Parameters:

Return value in:

Control: .

Property: TEXT or DEFPROP

- Oystein -

Mike,

I think you just need a crash course on the essential differences between OI's and AREV's methodology. While AREV continues to have some features that are hard to replicate in OI, OI is still hands down the better environment to develop in. Once you've mastered the basics, you'll be dreaming up of all kinds of different ways of creating forms and functionality. As a for instance, your "collector window" driven interface might be better suited with a "wizard" approach…and this is nothing more than a fancy non-databound OI window with a dialog box frame!

But on to your direct questions. I'm wondering if the reason your popup isn't popping up (assuming this is the problem vs. nothing being returned from a selection) is because you don't have a menu item in your window which is calling the OPTIONS event. One of the biggest differences between AREV and OI is that functions keys (e.g. F9, F8, F2, etc.) are built into AREV forms while OI must have these established as accelerator keys within a menu item. A major reason for this, of course, is so you can re-define these key strokes (or add new ones). If you are creating "collector" style OI windows then perhaps you removed all the menu items. If so, then F2 or Alt-Down (OI's default) won't do anything at all. You would then need to re-create a menu, assign it your preferred keystroke, and configure the QuickEvent to send the OPTIONS event to @FOCUS. You can make this menu invisible so the end user never sees it but it will still be fully functional.

I'm not sure what you mean by "variables" in your other question. I take it you mean things like @PSEUDO or @RECORD…which don't exist in OI (well, @RECORD does but not quite the same way.) All data information is retrieved by using the Get_Property function. This can be done from any program as long as you are passing it the correct name of the running window and control you want information from.

Hopefully this took you in the right direction. Either way, post again if you need further assistance.

[email protected]

SRP Computer Solutions

Thanks for the replies.

The popup in question does work, it is used in a form with a table attached.

On the form with no table attached, the edit-line option event looks exactly like the one on the form with a table and the popup event.

As another test I added a lostfocus event on the same editline to execute the same popup and this does work…..

I feel it has to do with the no table element, in that it seems OK on forms with tables.

Mike

Mike,

…looks exactly like…

What is your Return value in: Control: setting? If it's . they should look different, because the names of the two windows are different, perhaps the control names too. Perhaps you just copied the edit box from first window to the second and got the old settings?

(But of course you can use Return value in: Control: @SELF. Forgot to mention that in my last reply. @SELF will fit equally well everywhere.)

I really doubt the problem has to do with table-bound or not.

- Oystein -

Mike,

Having a databound control or not is irrelevant to having a Popup work. Can you post for us the exact way your QuickEvent is structured?

[email protected]

SRP Computer Solutions

Thanks to all

The problem was resolved when I put back the option menu item.

View this thread on the forum...