Skip to content

Commit 8e51433

Browse files
sbraconniertonygermano
authored andcommitted
Use type-appropriate renderer for custom metadata columns in message browser
This fixes what was apparently a regression bug in Mirth 3.2.0 introduced by commit 70eba57. It restores the functionality to display the contents of custom metadata columns in a format appropriate to the column type rather than always using the default MessageBrowserTextCellRenderer for non-String types. Signed-off-by: Tony Germano <tony@germano.name> Commit-message-by: Tony Germano <tony@germano.name> Issue: #75 Related: nextgenhealthcare/connect#6203
1 parent 75ca77c commit 8e51433

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

client/src/com/mirth/connect/client/ui/browsers/message/MessageBrowser.java

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -382,6 +382,9 @@ public void loadChannel(MessageBrowserChannelModel channelModel) {
382382
MessageBrowserTableColumnFactory columnFactory = (MessageBrowserTableColumnFactory) messageTreeTable.getColumnFactory();
383383
for (int modelIndex = 0; modelIndex < columnList.size(); modelIndex++) {
384384
TableColumnExt column = columnFactory.createAndConfigureTableColumn(messageTreeTable.getModel(), modelIndex);
385+
if (modelIndex >= columnMap.size()) {
386+
columnFactory.configureCustomColumn(column, metaDataColumns.get(modelIndex - columnMap.size()).getType());
387+
}
385388
messageTreeTable.addColumn(column);
386389
}
387390

0 commit comments

Comments
 (0)