Thursday, December 04, 2008     Register | Login | Search | Contact Us
     
   
     
     

Many of you already received communications about the move of the Cadence user community into cadence.com. And many of you have already joined, with over 4000 registrations in the first two weeks.

The new Cadence Community enhances the ability of Cadence users to connect and collaborate. In addition to moving the community into cadence.com -- enabling single sign-on for community, Sourcelink and Cadence events -- the new site is organized around nine technology segments, giving you easy access to product information, training, forums and blogs. Some of the new features include:
  • Ability to respond to posts via e-mail
  • Technology-specific blogs
  • Latest Web 2.0 social networking capabilities
  • Public profile options
  • Private messaging
  • Friends lists
Visit the new Cadence Community today at www.cadence.com/community and join the discussions!

Registration note: Due to the scope of the enhancements and the new SSO registration system, we were not able to migrate existing cdnusers.org member accounts. So new registrations are required, but this enables a broader set of functionality we think you'll enjoy.

Forum note: Under the guidance of forum moderators, we have taken the 20+ cdnusers.org forums and consolidated them into 11 forums on the new site. Posts have been brought over so you can leverage that posting history. CDNusers forums will be set to read only starting 7/30, and cdnusers.org will be redirected to the new community on 8/4.

Best regards,
Mike and Tom

Michael A. Catrambone - Steering Committee Chairman
Distinguished Engineer
PCB/Mechanical
UTStarcom, Inc.

Tom Diederich
Cadence Community Manager
Home
Forums
Forums > Custom IC > Shared code - SKILL

Subject: field names from different forms will conflict with each other?
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
Tongju
Posts: 13
Online: User is Offline
7/11/2008 10:59 AM  
I am trying to create a form which includes a cyclic field. However, if I name the cyclic field 'mode, the initial value of this cyclic field will not be what I expect:

hiCreateCyclicField(?name 'mode
                               ?prompt "Mode:  "
                               ?choices list("a mode" "b mode" "c mode")
                               ?value "a mode"
                               ?defValue "a mode"
                             )

After the form created, the formH->mode->value did NOT give me the string "a mode". Instead, it gave me the string in a old form that is for another application, which happen to have similar cyclic field called 'mode.

If I change the name of cyclic field, things come back to be normal. For example, if I just simply modify above code into:

hiCreateCyclicField(?name 'mode_test
                               ?prompt "Mode:  "
                               ?choices list("a mode" "b mode" "c mode")
                               ?value "a mode"
                               ?defValue "a mode"
                             )


then, formH->mode_test->value will give me "a mode", which is what I am expecting.

Will field name from different forms conflict with each other? How do I prevent it?

Thank you for your help in advance!

Tongju
ahamlett
Posts: 28
Online: User is Offline
7/11/2008 2:01 PM  
Yes, the form mode is global to that Cadence session so you will have to rename your form.

Try something like 'TJmode
http://83p.unitedti.org
Tongju
Posts: 13
Online: User is Offline
7/11/2008 4:18 PM  
Thank you, ahamlett, for your advice!

It turned out to be my own mistake. In my create application form wrapple, I have a function to re-load the values for fields if it found the same field from saved option file. Since this new form is very similar to the old form, it loaded back-in the value for the "mode" field from saved option file of the old form. When I looked at the CDS.log* carefully, I found the warning message " hiCreateCyclicField: value must be within the choice list. Setting to first choice.", which must come from my re-load code (putprop item aString 'value) because I have changed the choices in the new form. However, when I check formH->mode->value, it still keep the old value (the one from saved option file, but not in the new choices), which confused me ealier to let me believe hiCreateCyclicField is doing something wrong.

Tongju
Posting to forums is available to community members only.
Login or Register
Forums > Custom IC > Shared code - SKILL > field names from different forms will conflict with each other?


ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.