Problem with MSG (OpenInsight Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[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]]


==== Problem with MSG (OpenInsight Specific) ====
=== At 11 OCT 2000 01:56:12PM Donald Bakke wrote: ===
 
{{tag>"OpenInsight Specific"}}
 
<QUOTE>
Will somebody please test the following line of code and tell me what you get:



call msg(@window, "My email is don@paramount.com")



I believe there is unique bug in Msg. The "@PARAM" in the above email address is getting substituted like a replaceable parameter.



dbakke@srpcs.com

[url=http://www.srpcs.com]SRP Computer Solutions[/url]
</QUOTE>
----

=== At 11 OCT 2000 03:15PM Oystein Reigem wrote:  ===

<QUOTE>Don,



Neat.



For variations try [i]bill@windows.com[/i] and [i]jane@selfridges.com[/i].



Note that with [i]don@paramount.com[/i] the [i]o[/i] that follows [i]@param[/i] gets eaten. I think [i]@paramo[/i] (and possibly any [i]@param[/i]) gets interpreted as [i]@param0[/i]. [i]@param[/i] is buggy too but not so interesting. [i]@param1[/i] crashes the engine. To avoid fatal problems with your app I recommend you buy all possible domain names containing [i]@param1[/i] immediately.



- Oystein -

</QUOTE>

----

=== At 11 OCT 2000 04:37PM Agent C wrote:  ===

<QUOTE>[i]To avoid fatal problems with your app I recommend you buy all possible domain names containing @param1 immediately.[/i]







Agent C

</QUOTE>

----

=== At 12 OCT 2000 04:12AM Oystein Reigem wrote:  ===

<QUOTE>Sorry, Don. I didn't mean to poke fun at you. I just didn't know if I should laugh or cry. I chose to laugh.



- Oystein -

</QUOTE>

----

=== At 12 OCT 2000 07:44AM Oystein Reigem wrote:  ===

<QUOTE>C,



[i][/i]



Really? Have I soon deserved the right to sign with [i]Polly Puffin[/i]?



- Oystein -

</QUOTE>

----

=== At 12 OCT 2000 09:12AM Donald Bakke wrote:  ===

<QUOTE>Oystein,



No worries, I laughed (at least on the inside). My issue at that moment was meeting a deadline for deployment yesterday. FWIW, I was able to duplicate the problem for any window using a CreateParam parameter. This meant that I could not create a workaround to MSG since MSG itself is not the problem.



My only solution (unless someone has a better idea) was to check to see if "@param" appears in the message text. If so, I insert a space before and after the @ symbol so it looks like this: dbakke @ paramount.com.



Oh well...



dbakke@srpcs.com

[url=http://www.srpcs.com]SRP Computer Solutions, Inc.[/url]

[img]http://www.srpcs.com/srpicon1.gif[/img]

</QUOTE>

----

=== At 12 OCT 2000 01:20PM Don Miller - C3 Inc. wrote:  ===

<QUOTE>'Nother Don ..

FWIW, there are other gotcha's when using any word prefixed with an @-sign.  The compiler will certainly cough on it; in windows it is treated as a user-defined global @MYSTUFF which I use to save the create-parm; R/LIST can get lost and hang up.  It's like an * in a key when there ain't no 2-part keys defined.  Just try to get that back!

UUUUUUUUUUgly in the extreme.

Don Miller

C3 Inc.

</QUOTE>

----

=== At 12 OCT 2000 06:57PM Oystein Reigem wrote:  ===

<QUOTE>Don M,



It wasn't difficult to repeat Don B's experiment, but what's all the other @ stuff you're talking about?



- @ystein -





</QUOTE>

----

=== At 13 OCT 2000 03:59AM Simon Wilmot wrote:  ===

<QUOTE>Don,



I tried this and didn't get the problems you seem to be experiencing, although it wasn't working as I expected.



I did find more success using Msg2 however (Msg2 is the previous version of Msg that RTI saved within the system).



Might be worth trying that



Simon

Rebus Software (UK) Ltd

</QUOTE>

----

=== At 13 OCT 2000 09:21AM Don Miller - C3 Inc. wrote:  ===

<QUOTE>Oystein ..

For a long time Rev has used the Pick convention of treating system variables as having an @-sign prefixing reserved-word variables. Some examples are @RECORD, @ID, @DICT, @USER, @RECUR, @RECCOUNT, @ANS, @FILTER,@LIST.ACTIVE, @SAVE.SELECT, @LOWER.CASE, @UPPER.CASE, @FILES, @VOLUMES, @USERNAME, @LPTRHIGH, @LPTRWIDE and who knows what else are system variables.  If they were treated as regular variables, things could get messed up in a hurry.  My suspicion is that some of the OI code treats anything prefixed with an @-sign as being a "reserved" word.  Ditto with the windows convention of the &-sign.  Our scheduling product Schedule People & Time or SP&T, fondly known as SPIT, give us fits when coding messages, etc. for display.  Hot keys, etc.



Don Miller

C3 Inc.

</QUOTE>

----

=== At 15 OCT 2000 04:16PM Oystein Reigem wrote:  ===

<QUOTE>Don,



Can you use the Message_Box function instead? (Or the Windows MessageBox function.) It seems to display [i]don@paramount.com[/i] ok.



- Oystein -

</QUOTE>

----

=== At 15 OCT 2000 04:23PM Oystein Reigem wrote:  ===

<QUOTE>Don,



Didn't know about the problem with [b]&[/b] in Msg. But try [b]&&[/b] - e.g [b]SP&&T[/b].



- Oystein -

</QUOTE>

----

=== At 15 OCT 2000 04:34PM Oystein Reigem wrote:  ===

<QUOTE>Don,



[i]My suspicion is that some of the OI code treats anything prefixed with an @-sign as being a "reserved" word.[/i]



At least with Msg it's not "anything". It's just the various @-stuff you can use in quickevents - @Window, @Self, and @Param0 through @Param9. (Or to be more precise about the @Param ones: OI seems to check for just @Param and treat the next character as 0 if it's not a digit.)



But I'd be grateful if you can give me a couple of specific examples of the other problems you're talking about. (I assume you read my response about & in Msg, but you seem to have others up your sleeve.) Sorry if I seem slow.



- Oystein -

</QUOTE>

----

=== At 18 OCT 2000 11:52AM Don Miller - C3 Inc. wrote:  ===

<QUOTE>Oystein ..

See what happens if you accidentally put @DICT into MSG.  You'll love it after you reboot your machine!  Since you are probably better qualified about MSG in OI, I may have mis-spoken about all the @-variables.  Given what I know about RTI, though, it would not have surprised me in the slightest if the MSG call (vs. MSG2 by the way) might misinterpret @-variables.  I did note the @PARM ignoring 1-9 and assuming 0 .. what a wonderful assumption ..  I'm much more used to the AREV @-vars, though.  BTW, I know about SP&&T.  When I'm in a hurry, I tend to forget.

Cheers..

Don Miller

C3 Inc.

</QUOTE>

----

=== At 18 OCT 2000 02:39PM Oystein Reigem wrote:  ===

<QUOTE>Don,



[i]See what happens if you accidentally put @DICT into MSG[/i]



All right - since I'm closing down now anyway. It's getting late around here. :-)



- Oystein -

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=5FD662BA3700695485256975006287BE|View this thread on the  forum...]]