Re: Table field behavior -- make it not scroll!

Eric -- Thank you very much for your help. I also realize that my frustration is probably showing through in these emails. It get the most frustrated when what I think should be a simple thing turns out to be not so simple. Please keep working on your example stack as we really need those table

Re: Table field behavior -- make it not scroll!

That doesn't solve behavior. It still automatically scrolls when you get to the the last cell near an edge. I think I will make the field huge beyond the size I need and then hide the edges with graphics then it won't be able to do the automatic scroll as the field will be large enough so it won't

Re: Table field behavior -- make it not scroll!

Hi Bill, 1. In my example stack, the table field scrolls if neccessary depending on the number of columns and rows you want to display. 2. I think that you can simplify the handlers (a good idea, is not it?) by commenting the 2 SetScroll lines in the SelectCell handler. It should do the job in

Re: Table field behavior

On 5/20/05 11:01 AM, [EMAIL PROTECTED] wrote: I don't think the table field will get the RawKeyDown message as it goes straight to the card. It works okay for me in a field here, the field responds. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http

Re: Table field behavior -- make it not scroll!

I tried it again with the properties set by hand in the property pane of the field. Rev didn't crash this time but the field still scrolls although you can tab through things correctly, mostly. But playing with it causes a long wait. Is there anyone who knows how to just lock the tab cells in a ta

Re: Table field behavior

I don't think the table field will get the RawKeyDown message as it goes straight to the card. >>What if you place the code in the script of the field in question and then not have to worry about the name of the field or about it being called when doing stuff in other fields which may not want

Re: Table field behavior

Le 20 mai 05 à 17:06, Bill a écrit : Like so: ON OPENFIELD SET the xLimit of fld "VoyagesData" TO 6 SET the yLimit of fld "VoyagesData" TO 22 end OPENFIELD No. Just set these properties "by hand" in the property pane or in a handler which does not interfere with the table field as openField

Re: Table field behavior

On 5/20/05 8:41 AM, Lynch, Jonathan wrote: I find the current table fields just too clunky. I am creating a table object based on grouped fields. Been there, done that. :) If the hqx format doesn't work for you, let me know. Mine works prett

Re: Table field behavior

Like so: ON OPENFIELD SET the xLimit of fld "VoyagesData" TO 6 SET the yLimit of fld "VoyagesData" TO 22 end OPENFIELD And it just crashed bring down RunRev... On 5/20/05 10:53 AM, "Eric Chatonet" <[EMAIL PROTECTED]> wrote: > Hi Bill, > > Did you create the 2 custom properties xLimit and

Re: Table field behavior

Hi Bill, Did you create the 2 custom properties xLimit and yLimit in your table field which specify the limits? xLimit = the number of columns yLimit = the number of rows And set your table field to show the same number of columns and rows? Hope this helps! Le 20 mai 05 à 16:47, Bill a écrit : I

Re: Table field behavior

I think what I am looking for is in here: on SetScroll -- sets the table field and header fields scrolls if they are any -- the syntax is not very comprehensible since this handler can set the scroll of an unknown number of fields -- then it refers to parameters by order/number and not b

Re: Table field behavior

I put in your code and now the tab or arrow key makes the cursor go through the data fields correctly but the table still does that annoying automatic scroll that makes it data scroll off to invisible land when your are at the last cell. How do you lock the table grid so it does not scroll? On 5

Re: Table field behavior

st. > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Bill > Sent: Friday, May 20, 2005 9:27 AM > To: How to use Revolution > Subject: Re: Table field behavior > > Wow -- can't we make this any more complicated? > >

Re: Table field behavior

Bonjour Eric, Le 20 mai 05 à 15:27, Bill a écrit : Wow -- can't we make this any more complicated? I don't think so :-) we can! At least RunRev is working on it! But maybe Kevin meant something else in the rev-chat some weeks ago... ;-) Take care of carriage returns often added in mails, object'

Re: Table field behavior

Hi Bill, Le 20 mai 05 à 15:44, Bill a écrit : What if you place the code in the script of the field in question and then not have to worry about the name of the field or about it being called when doing stuff in other fields which may not want affected? Don't forget that I only made a copy/past

Re: Table field behavior

What if you place the code in the script of the field in question and then not have to worry about the name of the field or about it being called when doing stuff in other fields which may not want affected? On 5/20/05 9:17 AM, "Eric Chatonet" <[EMAIL PROTECTED]> wrote: > Hello Bill, > > I am w

RE: Table field behavior

down, then destroys those fields/groups as the row dissappears from view when it is scrolled past. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Sent: Friday, May 20, 2005 9:27 AM To: How to use Revolution Subject: Re: Table field behavior Wow

Re: Table field behavior

Le 20 mai 05 à 15:27, Bill a écrit : Wow -- can't we make this any more complicated? I don't think so :-) Take care of carriage returns often added in mails, object's names, custom properties to implement and take heart! Best regards from Paris, Eric Chatonet. ---

Re: Table field behavior

Wow -- can't we make this any more complicated? Thanks a whole lot. I will put your code in right now and start in as that automatic scroll thing is annoying as ^([EMAIL PROTECTED] (if you curse in unicode than no one will see). On 5/20/05 9:17 AM, "Eric Chatonet" <[EMAIL PROTECTED]> wrote: >

Re: Table field behavior

Hello Bill, I am working on a How-To stack about table fields. It's not finished but here is an excerpt from this stack which might help you without waiting for the release :-) As you will see it, it's a little bit dry and tricky :-( But fully commented :-) Following scripts are placed in the car