EditZoom_Equates (OpenInsight Specific)
At 22 AUG 2001 05:23:42PM a becker wrote:
Where can I find a copy of EditZoom_Equates?
I got the source, but when I tried to compile it, it tells me that EditZoom_Equates ain't anywhere to be found.
I wish to use this on an edittable so the cell can be expanded and allow the user to see and add wording in the cell rather that the first 20 or so characters that I am displaying and making life miserable. To bad when you hit the F2 function key (at least I think it is the F2 key, don't quote me on it), it don't automatically do this.
Thanks for your help
Andy Becker
Il. State Lottery
At 23 AUG 2001 08:54AM Don Miller - C3 Inc. wrote:
Andy..
Here is the version of Zoom that I use. There is only an $insert for the Logical block. The associated form is pretty simple..a text box, Ssave, Exit, Print buttons. The print routine does a little formatting & indenting using OIPI, but doesn't really matter much ..
beginning of function
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 nullTo make Zoom only work in EDITTABLES, comment out the Type1,4 line*/
begin case
case Type=EDITTABLE"Aux=Get_Property(Ctrl, "SELPOS") ;* where the text iscase Type1,4=EDIT"Aux="case 1returnend 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 thenDisplay the ZOOM window as a dialog box and pass in to the ZOOMwindow's CREATE event the "text" (DEFPROP) from the control withfocus. */Orig=Get_Property(Ctrl,"DEFPROP",Aux)
Text=Dialog_Box("ZOOM",Parent,Orig) ;* call the dialog box
/* 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
end of function Don Miller C3 Inc. </QUOTE> —- === At 23 AUG 2001 09:15AM a becker wrote: === <QUOTE>Thanks Don, I'll give it a shot. </QUOTE> —- === At 23 AUG 2001 02:21PM a becker wrote: === <QUOTE>Don Is this a stored procedure that gets added to the stored procedure area? We have looked at it and are a little puzzled. Thanks Andy </QUOTE> —- === At 23 AUG 2001 02:33PM Don Miller - C3 Inc. wrote: === <QUOTE>It's a stored procedure. You can call it from any Editxxx control in a form or from a program (for that matter) via a script: XXX=' CALL ZOOM(XXX) Or from a Program … Initialize parent with @WINDOW or wherever the program is running REPORT.REC contains a @TM delimited structure You have to declare DIALOG_BOX as a fucntion in the program STUFF=DIALOG_BOX("ZOOM",PARENT,REPORT.REC) HTH Don Miller C3 Inc. </QUOTE> —- === At 23 AUG 2001 08:16PM Scott, LMS wrote: === <QUOTE>Hi Don That zoom thing looks like the perfect candidate for a promoted event. Is there an event or would you hang it off the char event… And what does the help on the Char event mean when it reads "Not all keystrokes generate a CHAR event. To execute an event for keys which do not generate the CHAR event, create menu items with the desired accelerators." Which keystrokes don't? Nothing is ever simple. Scott </QUOTE> —- === At 24 AUG 2001 07:42AM Oystein Reigem wrote: === <QUOTE>Scott, I think it's like this: Alt+ keystrokes don't generate CHAR events. I think they by default are assumed to be accelerators and meant to be handled by menus. Even when they aren't. But that's perhaps fair enough. Also keystrokes you explicitely set up as accelerators don't generate CHAR events. E.g, if you set Ctrl+A to be an accelerator for some menu item, Ctrl+A won't generate a CHAR event. But that's what you should expect. Tab doesn't generate a CHAR event either. (Unless you have just one control in your form. Which is unlikely.) Don't know if I forgot anything. - Oystein - </QUOTE> —- === At 24 AUG 2001 09:25AM Don Miller - C3 Inc. wrote: === <QUOTE>Scott .. I thought about that early on. My problem is that I use it in several ways. On EditLine controls I hook it to an F3 key (just like tatty old AREV did). However, on EditTable controls I hook it to a Double-Click event for the Text portion of the table. The Double-Click event for EditTables for me is a kind of fit-all-finger ring. When I'm on a Date field, I call a Calendar, on other things I hook it to a Popup which, when selected, populates other information in the same row, etc. For many items, I allow a text field for Notes / Comments for the item. That is where Zoom is handy. My Zoom form has a couple of Hidden Menu options that allow for auto-date stamping (ALT+1) and formatted print (ALT+2). The same Zoom form is called from either an EditLine or EditTable regardless. Don Miller C3 Inc. </QUOTE> —- === At 28 AUG 2001 03:28PM cp wrote: === <QUOTE> <code> <code> compile insert EditZoom_Equates * * This program is proprietary and is not to be used by or disclosed * to others, nor is it to be copied without written permission from * Revelation Technologies, Inc. * * Name : EditZoom_Equates * Description: Instructions and constants for the EditZoom function * * History : * 10/25/97 cp Original programmer * **
declare subroutine EditZoom declare function EditZoom
* instructions equ EZCMD_ZOOM$ to 1 ;* EditZoom(EZCMD_ZOOM$, CtrlEntID) equ EZCMD_ISZOOMABLE$ to 2 ;* bCanZoom=EditZoom(EZCMD_ISZOOMABLE$, CtrlEntID) equ EZCMD_DIALOG$ to 3 ;* NewText =EditZoom(EZCMD_DIALOG$, OrigText) equ EZCMD_CREATE$ to 4 ;* reserved equ EZCMD_CLOSE$ to 5 ;* reserved equ EZCMD_SAVE$ to 6 ;* reserved equ EZCMD_DEL$ to 7 ;* reserved equ EZCMD_DATE$ to 8 ;* reserved equ EZCMD_TIME$ to 9 ;* reserved equ EZCMD_TOUPPER$ to 10 ;* reserved equ EZCMD_TOLOWER$ to 11 ;* reserved equ EZCMD_TOMIXED$ to 12 ;* reserved equ EZCMD_INDENT$ to 13 ;* reserved equ EZCMD_UNINDENT$ to 14 ;* reserved equ EZCMD_SIZE$ to 15 ;* reserved equ EZCMD_FONT$ to 16 ;* reserved equ EZCMD_BACKCOLOR$ to 17 ;* reserved equ EZCMD_FORECOLOR$ to 18 ;* reserved equ EZCMD_WORDWRAP$ to 19 ;* reserved
* structure of parameter passed to EZCMD_DIALOG$ equ EZPARM_TEXT$ to 1 equ EZPARM_READONLY$ to 2 ;* boolean, defaults to FALSE$ equ EZPARM_TEXTJUST$ to 3 ;* L, C, or R, defaults to L equ EZPARM_UPPERCASE$ to 4 ;* boolean, defaults to FALSE$ equ EZPARM_FONT$ to 5 ;* defaults to windows default font equ EZPARM_BACKCOLOR$ to 6 ;* defaults to white equ EZPARM_FORECOLOR$ to 7 ;* defaults to black equ EZPARM_SELSTART$ to 8 ;* defaults to 1 equ EZPARM_SELLENGTH$ to 9 ;* defaults to 0
* EditZoom INI keys equ EZ_INI_FILE$ to "OINSIGHT.INI" equ EZ_INI_SECT$ to "EditZoom" equ EZ_INI_SIZE$ to "Size"
</code>
</code>
At 29 AUG 2001 07:49AM Oystein Reigem wrote:
Now which Cool Programmer posted that?
- Oystein -
At 29 AUG 2001 08:41AM Simon Wilmot wrote:
I think there is a (large) hint given with the 'original programmer' comment
Simon
At 31 AUG 2001 12:09AM B Stevens wrote:
OK, now where can we get the EditZoom program
I am using Zoom from the KB article for EditTables, bit messy to implement. Is this one any better.
Barry
At 31 AUG 2001 05:43PM Oystein Reigem wrote:
I might need a zoom program too. I have something I made for an earlier app, but there is at least one weak point - when zoomed on an edit table cell nothing protects the user from entering data beyond the data length of the cell, and if he does so, data will be lost. How good are the two programs mentioned in that respect? (Silly question. Surely the authors of the zoom programs must have considered this problem.)
- Oystein -