[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]
==== Using system monitor to run or exec a form (OpenInsight Specific) ====
=== At 30 JUL 2001 11:19:58PM Scott, LMS wrote: ===
{{tag>"OpenInsight Specific"}}
Hi All
I sort of patched another hole in my lace doley of OI knowledge at the Melbourne Roadshow. Mike kept using System Monitor to run forms. So I asked Sprezz how to run the system monitor (Duh Tools|Advanced from the OI form).
So I try this at home. It opens my form in test mode, but when I click on the Run button (on my form) the commuter event does not run. And system monitor doesn't seem very helpful in its litany of events. None of them seem specific to my form. The form doesn't have any fields linked to the database, it's just an input device for the commuter stdproc.
My form runs fine if I open it in the form designer and do test run.
I was wondering if I needed more parameters or a different way of running the thing than
EXEC my_form_name
I'd appreciate any help on this, plus any pointers to where I can find out more about System Monitor - I believe there is a SENL with some useful stuff out there somewhere. Got to be more info out here somewhere than in the OI help. I tried a search here, but got as far as you can "RUN" things and "EXEC" things but not why mine didn't work.
Scott, LMS
----
=== At 31 JUL 2001 07:51AM WinWin/Revelation support wrote: ===
There is a Knowldge base article on the system monitor [url=http://www.revelation.com/WEBSITE/knowledge.nsf/07dbcbabb6b3e379852566f50064cf25/6ae1dfc185baab0d85256626004abd37?OpenDocument]here[/url]
Not sure why quickevent does not work.
Some other things you can do with system monitor
EXEC MyWindow to start your window
run set_property "MYWINDOW","TEXT","I changed the title"
to set a property. works with set or get of all properties
run send-event "MYWINDOW.MYBUTTON","CLICK" to fire events to your controls.
run or_view "","LIST MYFILE F1 F2 F3" to run rlist statements to a viewer
While developing a form you can leave it open in the form editor, save it, then exec it from the system montior to see the latest changes. In particular, if this is a form you run from an MDI frame,
exec the frame and leave it open, then work on the form in form designer, save the form but leave it open in form designer. Open the form from the menu of the frame to test it in the appropriate context. Compared to repeated;ly opening the form designer with different windows this saves time.
hope this helps
Bob
----
=== At 31 JUL 2001 09:35PM Scott, LMS wrote: ===
Hi Bob
Your link points to the system editor EXEC article. I found that in the knowledge base under functions/subroutines etc but I couldn't find a matching one about system monitor.
I will experiment further about the quick event problem. It is a puzzle why the System Monitor Exec wasn't running the commuter. At least I know now it isn't something I left out of the command.
The form in question is an established form I use as a development tool to report on controls, quickevents and event scripts attached to a form. I then use the output from this report on specified application forms as the basis to create new commuter events.
Its a bit recursive that my first attempts at commuter events was something to help me make commuter events.
The fact that this particular form is a development tool is the main reason why it would be nice if I could just run it from the system monitor instead of having to open it in Form designer. Hmm I wonder if the reason it didn't work properly was because I had it open in Form designer at the same time. If I figure it out, I will post here.
Scott, LMS
----
=== At 31 JUL 2001 09:48PM Scott, LMS wrote: ===
Hi all
Hmm, seems that the form runs better in system monitor when the same form is not open in form designer. Which, in this case suits me.
Other weirdness, while I'm about it - I had some edittable controls bound to columns in a table. Then I changed the table columns from single value to multivalue in the dictionary, because having single value controls bound to table columns didn't update correctly - they got cleared every time. Saving and compiling the form after doing the table dictionary update made no difference. In the end I had to unlink the edittable columns, save the form with the columns unlinked, then link them again. I guess it would be nice to have a "force binding update based on the dictionary" form save option.
I'd still like any more info on System MONITOR.
Thanks
Scott, LMS
----
=== At 02 AUG 2001 09:38AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote: ===
What sort of information are you looking for?
[url=http://www.sprezzatura.com/senl/volume1/v1i7.htm#_Toc447357926]SENL Volume 1, Issue 7[/url] and [url=http://www.sprezzatura.com/senl/volume1/v1i8.htm#_Toc447361862]SENL Volume 1, Issue 8[/url] have some information on the system monitor and how it behaves. Don't know if it's enough information for you.
The system monitor is actually always running. It is the process that makes everything work. It's sorta the link between the presentation server and the engine.
Part of your troubles could be related to the form designer and test run. I know that the test run on NT with the debugger active is a huge pain. It really only works if you execute the form from outside of the form designer.
[url=http://www.sprezzatura.com" ]The Sprezzatura Group[/url]
[i]World Leaders in all things RevSoft[/i]
[img]http://www.sprezzatura.com/zz.gif[/img]
----
=== At 02 AUG 2001 10:57AM Oystein Reigem wrote: ===
[i]The system monitor is actually always running.[/i]
I didn't know that. Or did i? :-) Is it common knowledge?
It half explains something I've asked about on the lists. I have a process that rebuilds a lot of indexes. Every now and then there's a beep. That must be when the System Monitor window is full and does a clear. I felt very certain the explanation must be something like that but I don't think I ever got it confirmed from Revelation or other list participants.
When I say "half" it's because there should also be beeps when other processes are running. Why not?
- Oystein -
----
=== At 03 AUG 2001 04:10AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote: ===
Oystien,
The beep you hear is the system monitor editbox hitting 32K and clearing itself down. When a Basic+ program uses the send_Info() function the system monitor displays the data sent (even if it's not visible) UNLESS you have a STATUSLINE property set in your window in which case it gets sent there instead.
An index rebuild uses a LOT of send_Info() calls, when other lengthy processes might not - that's why you may not hear anything from them.
[url=http://www.sprezzatura.com]The Sprezzatura Group[/url]
[i]World leaders in all things RevSoft[/i]
[img]http://www.sprezzatura.com/zz.jpg[/img]
[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=51D0A5A7224D988285256A9A00124F06|View this thread on the forum...]]