Baxter IT: Cursor navigation on screens.

[Joe Boyle]

I remember working on a similar problem once where conditional field
processing was performed in a numbered designer procedure very like the
example below. Ottawa’s advice was to change syntax "designer procedure 1"
to "designer procedure one" and change the ‘event for tab key in change
context’ for all relevant fields from "activate nxt field rbf"  to  "send".

There are many default field processes that occur when using syntax like
"designer procedure 1"  which result in automatic field order processing.
This is why Ottawa have recommended this alternative, using a button to
execute procedure written code blocks.

You might find the solution to your problem in this area. Try playing around
with the different options.

screen send_vs_nxtrbf   
       
temp t1 char *4 
temp t2 char *4 
temp t3 char *4 
temp t4 char *4 
temp t5 char *4 
temp t_flag reset at startup 

field t1 id 1     
field t2 id same     
field t3 id same     
field t4 id same     
field t5 id same     

procedure designer one
	begin
		accept t2 
		accept t5
		if t_flag =0
		 	then accept t1
		accept t4
		accept t3
	end
	
procedure designer onof
	begin
	  	 
if t_flag = 1
    then let t_flag = 0
    else let t_flag = 1

  	end


build list


Regards, Joe. 
________________________________________
From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
[mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On Behalf Of
Syed Shahul Hameed Mustaffa
Sent: 17 December 2005 05:44
To: Jeff Hoffman
Cc: powerh-l at lists.sowder.com
Subject: Re: Baxter IT: Cursor navigation on screens.

Thanks Jeff,
 
I tried the shift+tab. It is behaving strangely. The entry screen becomes
unstable. Instead of going to the previous field in a cluster, it is jumping
2 or 3 fields. If I use mouse, it is also giving me problems. I've to
mention something here. The field navigation is controlled by a
user-procedure which ACCEPTs field after field. Could this code controlled
navigation be the reason for this strange behaviour. 
 
Regards,
SYED.

 
On 12/14/05, Jeff Hoffman <wonicon at optusnet.com.au> wrote: 
Hi

You are on a different platform, things do change, not knowing anything
about axiant, shift tab would work for me. 

I was going to suggest you could use key mapping in your terminal emulator
to convert \\ to shift tab, but I woke up enough   before I sent that
version of the reply, aaah for the good old days....

Jeff 

At 10:16 PM 14/12/2005, you wrote:
>Thank you Glenn.
>You're correct. It worked.
>
>Can I have one more question please?
>
>The legacy application PH/MPEIX has a feature of entering a \\ (double 
>backslash) to go to the previous field.
>It doesn't work in the Axiant Appication.
>Is there any way to bring back this feature? The business seems to be very
>particular about it.
>
>Thanks again for your valuable help. 
>Regards,
>SYED
>
>
>On 12/14/05, Glenn Baxter
><<mailto:Glenn at baxterit.com.au>Glenn at baxterit.com.au > wrote:
>Hi Syed,
>I have generated a default "Screen1" on a table.
>It behaves the same.
>In character mode, you have an action box, and the cursor returns there;
>unless you have autoupdate or such. 
>In Axiant, with no Action Box, the cursor goes round and round!
>
>You can, on the last field on the screen alter the Return Key, Prompt
Context
>Default Return Key Event - Activates next RFB {Rapid Fire Block} 
>Changed to Return to Action - Quick Commands
>
>See how that goes!
>Sincerely
>Glenn Baxter
>=======================
>Baxter IT Solutions Pty Ltd
>456 Victoria Parade, East Melbourne 
>Victoria, Australia 3002
>p: 03-9415-8733
>m: 0412-826-503
>f: 03-9415-8911
>e: glenn at baxterit.com.au
>=======================
>
> 
>
>----------
>From: Syed Shahul Hameed Mustaffa [mailto:sshahulgm at gmail.com]
>Sent: Tuesday, 13 December 2005 7:10 PM
>To: PowerHouse List
>Cc: Joe Boyle 
>Subject: Cursor navigation on screens.
>
>
>
>
>On 12/13/05, Syed Shahul Hameed Mustaffa
><<mailto:sshahulgm at gmail.com> sshahulgm at gmail.com > wrote:
>Dear Gurus,
>
>Quick Intro: I've migrated a PH/MPEIX application to AXIANT4GL/WINDOWS
>(Thin Client).
>
>In some of my screens, after the cursor reaches the last field, instead of 
>going to the action mode it goes to the first field.
>What is causing this behaviour? How can I stop it?
>
>Thanks in advance for any effort to sort this issue out.
>
>Best Regards,
>SYED.
>
>
>
>--
>= = = = = = = = = = = = = = = = = = = = = = = = = = = =
>Mailing list: powerh-l at lists.sowder.com
>Subscribe: "subscribe" in message body to powerh-l-request at lists.sowder.com
>Unsubscribe: "unsubscribe &lt;password&gt;" in message body to
> powerh-l-request at lists.sowder.com
>http://lists.sowder.com/mailman/listinfo/powerh-l
>This list is closed, thus to post to the list you must be a subscriber. 

--
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l at lists.sowder.com
Subscribe: "subscribe" in message body to powerh-l-request at lists.sowder.com
Unsubscribe: "unsubscribe &lt;password&gt;" in message body to
powerh-l-request at lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.