Stats

  • Locked Locked
  • Replies 5
  • Subscribers 145
  • Views 14968
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Set Focus

useratcad

 Hello,

I have a StringField, that looks like this:

hiCreateStringField(
                    ?name 'Test
                    ?prompt "Folder of Test File:.............................................."
                    ?value mvalue
                    ?invisible list(nil)
                    ?callback "checkDirEx( )"
                 )

 where my callback-routine looks like that:

 procedure(checkDirEx()
  prog(()
    
      if(!isDir(MyForm->Test->value) then
        if(hiDisplayAppDBox(
              ?name 'questMsgDBox
              ?dialogStyle 'modal     ; wait for user-interaction before continuing
               ?dboxBanner "Directory not found"
              ?dboxText sprintf(nil "Warning: the entered path does not exist.\nWould you like to change it?" )
              ?dialogType hicQuestionDialog
              ?buttonLayout 'YesNo)==t then    
            Test->focus=t

           )
    )
          
 
  )
)

Is there a way to set to Focus to a field?

Parents
  • I would implement it in this way:
     - The string field calls the 'checkDirEx' callback.
     - The 'checkDirEx' sets the field to highlight an error if the directory does not
       exist and displays the 'Yes/No' dialog, I come to this more specific below.
       The question here is:
        "Warning: The entered path does not exist. Would you like to change it?"
       It is pretty obvious that one would to change it if it does not exist, isn't it?
       What should happen if the user selects 'No', you didn't tell that, should the
       directory be created then. This has an influence on you callback structure.
       So I decided in my example to just fire a warning and did no questionnaire.

     - And hence I  realized that the 
       'hiSetCurrentField' seems to have not effect, neither in the
       'hiDisplayAppDBox' callback nor in the string field callback 'checkDirEx'.
       The field focus always seems to be be on the field where you cursor was
       positioned before the dialog box pops up.

    procedure( checkDirEx( r_formDataStruc )

    when( !hiIsInFieldCancel( )
      if( isDir( r_formDataStruc->r_validStringField->value ) then
        hiHighlightField(
    		r_formDataStruc
    		'r_validStringField
    		'background
    		)
        nil
      else		
        hiHighlightField(
    		r_formDataStruc
    		'r_validStringField
    		'error
    		)
        hiDisplayAppDBox(
                   ?name        'warningDialog
                   ?dboxBanner  "Directory not found"
                   ?dboxText    strcat( 
    	                          "Warning: The entered path \"" 
    				  r_formDataStruc->r_validStringField->value 
    				  "\" does not exist.\n" 
    				  )
                   ?dialogType  hicWarningDialog
                   ?buttonLayout 'Close
    	       ?callback "hiSetCurrentField( hiGetCurrentForm( ) 'r_validStringField )"
        ) 
        t
      ) ;; close if
    ) ;; close when
    ) ;; close procedure


    procedure( UIcreateMyForm( )
        let( ( r_validStringField r_dummyStringField )
        
    r_validStringField = hiCreateStringField(
                            ?name       'r_validStringField
                            ?prompt     "Folder of test file: "
                            ?value      ""
                            ?callback   "checkDirEx( hiGetCurrentForm( ) )"
                            )
    			
    r_dummyStringField = hiCreateStringField(
                            ?name       'r_dummyStringField
                            ?prompt     "Just a dummy field: "
                            ?value      ""
                            )
    			
    hiCreateAppForm(
    	?name		'_myForm_	
        	?formTitle	"Field Focus Test"
    	?initialSize	list( 300 80 )
    	?fields		list(
    				list(
    					r_validStringField
    				 	15:5 250:25 120
    					)
    				list(
    					r_dummyStringField
    				 	15:50 250:25 120
    					)
    			)
    	?attachmentList	list(
    			        ( hicLeftPositionSet|
    				  hicRightPositionSet
    				)
    		                ( hicLeftPositionSet|
    				  hicRightPositionSet
    		                )
    			) 
    )

    ) ;; close let 
    ) ;; close procedure


    procedure( UIfieldFocusTest( )

        unless( boundp( '_myForm_ ) && hiIsFormDisplayed( _myForm_ )
            UIcreateMyForm( )
        )
            
        hiDisplayForm( _myForm_  )
     
    ) ;; close procedure
Reply
  • I would implement it in this way:
     - The string field calls the 'checkDirEx' callback.
     - The 'checkDirEx' sets the field to highlight an error if the directory does not
       exist and displays the 'Yes/No' dialog, I come to this more specific below.
       The question here is:
        "Warning: The entered path does not exist. Would you like to change it?"
       It is pretty obvious that one would to change it if it does not exist, isn't it?
       What should happen if the user selects 'No', you didn't tell that, should the
       directory be created then. This has an influence on you callback structure.
       So I decided in my example to just fire a warning and did no questionnaire.

     - And hence I  realized that the 
       'hiSetCurrentField' seems to have not effect, neither in the
       'hiDisplayAppDBox' callback nor in the string field callback 'checkDirEx'.
       The field focus always seems to be be on the field where you cursor was
       positioned before the dialog box pops up.

    procedure( checkDirEx( r_formDataStruc )

    when( !hiIsInFieldCancel( )
      if( isDir( r_formDataStruc->r_validStringField->value ) then
        hiHighlightField(
    		r_formDataStruc
    		'r_validStringField
    		'background
    		)
        nil
      else		
        hiHighlightField(
    		r_formDataStruc
    		'r_validStringField
    		'error
    		)
        hiDisplayAppDBox(
                   ?name        'warningDialog
                   ?dboxBanner  "Directory not found"
                   ?dboxText    strcat( 
    	                          "Warning: The entered path \"" 
    				  r_formDataStruc->r_validStringField->value 
    				  "\" does not exist.\n" 
    				  )
                   ?dialogType  hicWarningDialog
                   ?buttonLayout 'Close
    	       ?callback "hiSetCurrentField( hiGetCurrentForm( ) 'r_validStringField )"
        ) 
        t
      ) ;; close if
    ) ;; close when
    ) ;; close procedure


    procedure( UIcreateMyForm( )
        let( ( r_validStringField r_dummyStringField )
        
    r_validStringField = hiCreateStringField(
                            ?name       'r_validStringField
                            ?prompt     "Folder of test file: "
                            ?value      ""
                            ?callback   "checkDirEx( hiGetCurrentForm( ) )"
                            )
    			
    r_dummyStringField = hiCreateStringField(
                            ?name       'r_dummyStringField
                            ?prompt     "Just a dummy field: "
                            ?value      ""
                            )
    			
    hiCreateAppForm(
    	?name		'_myForm_	
        	?formTitle	"Field Focus Test"
    	?initialSize	list( 300 80 )
    	?fields		list(
    				list(
    					r_validStringField
    				 	15:5 250:25 120
    					)
    				list(
    					r_dummyStringField
    				 	15:50 250:25 120
    					)
    			)
    	?attachmentList	list(
    			        ( hicLeftPositionSet|
    				  hicRightPositionSet
    				)
    		                ( hicLeftPositionSet|
    				  hicRightPositionSet
    		                )
    			) 
    )

    ) ;; close let 
    ) ;; close procedure


    procedure( UIfieldFocusTest( )

        unless( boundp( '_myForm_ ) && hiIsFormDisplayed( _myForm_ )
            UIcreateMyForm( )
        )
            
        hiDisplayForm( _myForm_  )
     
    ) ;; close procedure
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.