I tried to recreate the zoom function in OI by following the document provided on RTI's site (Creating Zoom Functionality…Novermber 1997).

As far as I can tell, I've followed the instructions. This is what happens when I press the F3 accelerator key.

First time: "FS100 Record %1% does not exist"

Next time and all subsequent time: "The Entry is locked and may not be modified. Do you wish to continue to view the entity."

Also when I don't hide the menu option "Zoom", I see the words "F3" and "Zoom" sqeezed together when the form is runned. In design mode, all I see is "Zoom".

Does any one have any ideas or suggestions. Thanks.

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

Ray,

What doc are you talking about? I looked in the knowledge base for nov97 and found no 'zoom'.

dsig@teleport.com onmouseover=window.status=imagine … a company that supports it products with pride not extortion;return(true)"

David Tod Sigafoos ~ SigSolutions

cell: 503-341-2983

Dave,

If you do a search on "zoom", you will see that the first item is titled "OIDownload". You will find the zoom article contained in that document. Below is the URL:

http://www.revelation.com/8525654e004e75de/d739a1010f28f6798525656b00612ab1/e96bfcaf8023329685256562004b876d?OpenDocument

Thanks,

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

Ray,

It might be easier to tell us exactly what you want to accomplish with a zoom feature. There really are various ways of approaching this and some are better sooted for specific intents.

dbakke@srpcs.com

SRP Computer Solutions

Ray,

That is in the "works" section. Remember JA wanted me off the works because he didn't like me saying there were problems and that you shouldn't have to pay (actually i think i might have used the word extortion to get fixes .. no really .. He did promise to have many of the problems fixed but of course I never did get the fixes. Oh well.

So .. if you have a copy of the article email off to me.

dsig@teleport.com onmouseover=window.status=imagine … a company that supports their product from pride not extortion;return(true)"

David Tod Sigafoos ~ SigSolutions

dsig@teleport.com Cell:503-341-2983

Dave,

Sorry about your situation with RTI/JA. Well I don't think it's unreasonable to expect problems to be fixed. I hear you. I know that many other developers have concerns regarding RTI's intention from time to time. FWIW, I post messages on this sections and the Works. In general, and I think that I am being fair when I say this, I get better help and support on this side of RTI's site than I do on the Work side and when I do get help on the WORK side it's mostly from regular, helpful, and experience developers such as yourself. I wish that RTI would pitch in more. I don't mean to say this in a nasty way, but it is a reality.

So I appreciate your help and the help of other AREV/OI developers. Without your and other presence this site would be less valuable.

I will try to find a copy of my Zoom thing and either e-mail it or fax it to you. Take a look at it and see if you can duplicate what I'm seeing. I believe that I have done everything, but I am only 'human' (from time to time).

Ray

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

Don,

]]What do I want to do with the zoom…Symmetry Info[/url]

Ray Chan ~ Symmetry Info

Ray,

I just want to be able to duplicate the zoom feature in AREV.

The Zoom feature in AREV was automated when the field for TEXT datatypes. As you have seen, this has to be specifically programmed in your application.

Assuming you want exact or near-quality funtionality to AREV here are the general steps to take:

1. Setup a menu called "Zoom" (or whatever) and assign it F3 as the accelerator key

2. Use the QuickEvent for this menu to call a stored procedure that will have all your zoom functionality

3. Write a stored procedure that will do the following:

a. Get the current control with FOCUS

b. Get this control's DEFPROP or INVALUE property

c. Launch a modal dialog box that passes the control's data through the CreateParam event

d. This modal dialog box will have an editbox to display the "full" data, an OK button, and a CANCEL button

e. Obviously the CREATE event of this dialog box will take the passed data and populate the editbox

f. The user can make changes as desired

g. If the user clicks on the OK button then take the contents of the editbox and pass back through using the End_Dialog box

h. Now your stored procedure will have these changes and you can set the DEFPROP/INVALUE property of the FOCUS control with these changes

4. Obviously this is a rough sketch but there should be enough for you to get a working skeleton. One significant issue will be EDITTABLES. In these cases you will want to get the SELPOS property as well and extract the specific column and row data rather than use the entire DEFPROP property

Speak old wise one.

Wise…maybe. Old…I hope not. Is 33 old these days?

dbakke@srpcs.com

SRP Computer Solutions

---

=== At 11 MAY 2000 10:25AM rayc@symmetryinfo.com wrote: ===

Don/Son,

]]Wise…maybe. Old…I hope not. Is 33 old these days?. (Just kidding RTI.)

From The Old One, but young at heart. Look I'm trying to use OI ain't I ;),

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

---

=== At 11 MAY 2000 02:02PM Don Miller - C3 Inc. wrote: ===

Ray ..

I have used a modified version of the RTI idea for ZOOM functionality all over the place in our app (DBTABLES, etc.). We have hooked it into a Double-Click event on DBTABLES to allow for multiple text lines in Multi-Valued items. If you post me your E-Mail address, I'll send you two pieces:

The Stored-Procedure that can be used to invoke the routine and the Code that goes on the Create event in the form. About the only problem I have is when the text gets bigger than 64K. In this case, I have to page it in and out.

* never mind .. here is the mainline stored procedure

* function Zoom(void) declare function Get_Property, Dialog_Box declare subroutine Set_Property $insert Logical * Get the control that has focus and its control TYPE Ctrl=Get_Property(@window, "FOCUS") Type=Get_Property(Ctrl,"TYPE") /* If the control is an edit table, get its position If the control Type begins with "EDIT" set the variable AUX to null To make Zoom only work in EDITTABLES, comment out the Type1,4 line */ begin case case Type=EDITTABLE" Aux=Get_Property(Ctrl, "SELPOS") case Type1,4=EDIT" Aux=" case 1 return end case /* This code assigns the window's control name or the MDIFRAME's control name to a variable. */ Parent=@window Frame=Get_Property(Parent,"MDIFRAME") if len(Frame) then Parent=Frame /* Get the default property "DEFPROP" for the control with focus; this is probably the text displayed in the control then Display the ZOOM window as a dialog box and pass in to the ZOOM window's CREATE event the "text" (DEFPROP) from the control with focus. */ Orig=Get_Property(Ctrl,"DEFPROP",Aux) Text=Dialog_Box("ZOOM",Parent,Orig) /* If the variable Text is not null and not equal to Orig, then the text (DEFPROP) is updated for the control with focus. */ if len(Text) and Text # Orig then Set_Property(Ctrl,"TEXTVAL",Text,Aux) end return Text ***

* here is the create parm

declare subroutine Set_Property, Send_Event

declare function Get_Property

* if you don't want to start maximized then comment out the next line

SET_PROPERTY(@WINDOW,"VISIBLE",3) ;* START MAXIMIZED

if len(CreateParam) then

.eb_Text-]TEXTVAL=CreateParam

end

RETURN 0

Don Miller

C3 Inc.

---

=== At 12 MAY 2000 12:31AM rayc@symmetryinfo.com wrote: ===

Don M,

Thanks for posting the code, et al. I looked at it and it was pretty much what RTI provided and what I was doing. This gave me some confidence that I was at least on the right track. So thanks.

Feeling better about myself ;), I decided to play with Zoom again. In the process I did two things: 1) I removed my Zoom from the top of the Menu (supposedly OI doesn't like this) and I changed the Assign key for an QBF item. F3 was step 6 in the RTI document. However, the F3 is already assigned to th QBF. So I changed it to prevent a possible conflict.

Voila after doing the above. Zoom works. I feel so stupid.

Is there a way to see a multivalue control, such as an Address field for example, e.g.,

4200 Mass Ave

Appt 5043

Right now, it shows just one line at a time. The AREV zoom showed all.

Thanks again,

Ray

P.S. Were you going to write a book or something in Spanish. I think I spoke to you some years ago back in the days of CompuServe.

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

---

=== At 12 MAY 2000 12:55AM Don Bakke wrote: ===

Ray,

It seems that you still need to zoom in a multi-valued control. Are you referring to data that is @TM delimited but stored in an edittable? If so, then the process is very similar to what you are already doing but you will focus on a specific cell of an edittable rather than the entire editline/editbox at once.

dbakke@srpcs.com

SRP Computer Solutions

---

=== At 12 MAY 2000 03:12PM Don Miller - C3 Inc. wrote: ===

Ray ..

You can pass whatever you want into ZOOM. So ..

foo=GET_PROPERTY(@WINDOW:".whatever control","DEFPROP")

* this might be multi-valued

SWAP @VM with @TM in foo

CALL ZOOM(foo)

* get whatever comes back

SWAP @TM with @VM in whatever_came_back

SET_PROPERTY(@WINDOW:".whatever control","DEFPROP",what_came_back)

RETURN 1 OR 0

For the other issue..

I have about 400 pages of manuscript and about 100 photos at a publisher. The book isn't in Spanish but is about MAYA sites in Mexico, Guatemala, Belize, and Honduras. Thanks for asking. I'll let you know if I get anywhere with this one.

Don M.

C3 Inc.

View this thread on the forum...