Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Categories DXL
Created by Guest
Created on Oct 19, 2023

Link Module Attribute with Dialog Box Element

Dear Sirs,

every time that I have to create a custom GUI (by means of DXL) to update attributes it is quite painful.

Below is report a classical example how I handle the synch between the attribute and the dialog box element:

Module mod = current
string modName = name mod

DB win = create(mod, "Link Module Attribute with Dialog Box Element")
DBE fld = field(win, "Prefix: ", mod."Prefix" "", 50)

/* callback function to update the module attribute using the value of the dialog box element */
void UpdateModAttr(DBE dbe)
{
mod.
"Prefix" = getBuffer dbe
return
}

/* callback function to update the dialog box element using the value of the module attribute */
void UpdateDBE(Trigger attrEvent)
{
set(fld, mod."Prefix" "")
return
}

/* set the callback function of each dialog box element of the collection */
setTextChangeCB(fld, UpdateModAttr)
trigger(module->modName->attribute->"Prefix", modify, 20, UpdateDBE)

realize win
show win

It would be nice to have this handing directly in the definition of the DBE.

In other worlds, instead to have:

DBE field(DB box, string label, string initial_value, int width[, bool read_only])

to have:

DBE field(DB box, string label, Attr__ synch_attribute, int width[, bool read_only])

or also to have the possibility to set it after the definition of the dialog box element:

set(DBE dbe, Attr__ synch_attribute)

Of course, not just for field dialog box element but for all other elements.

Idea priority Medium
Needed By Quarter