Profound Logic Forums

I have subfile fields which previously used the DSPATR(PC) keyword conditioned with an indicator. After conversion, these fields still receive the focus but the text cursor does not appear in the field under a certain condition. If I am changing an existing row in the grid, the text cursor appears as expected. When I add a new row to the grid, the text cursor does not display in the focused input field in that new row.

The difference is that for changes to existing rows the grid also has the focus. But, to add a new row to the grid I have to click a button which is outside the grid. Thus, even though I request the focus on the new grid row field, it seems that button I clicked is actually retaining the focus. Is there a workaround for this sequence of events? Thanks.

Hmmm... this is strange. From our frameworks perspective, there isn't a difference between records that you updated in your RPG vs. new records that you added. For each screen, all of the data is sent, and it builds the displays. It doesn't know that you previously displayed with fewer records, or that somewhere on the server they got changed, or anything like that, it just gets the data and draws the screen.

I can't see how it could retain focus on a button? In fact, some of our button widgets don't even really have the concept of "focus", like the CSS buttons for example, they're just <div> tags that have been styled to look like buttons. So not sure how that could happen.

Here's what I would do:

1) Your DSPATR(PC) attributes shouldbe converted to the "Set focus" property on your widgets. I would check them and make sure they have this property defined as expected, with the right indicator, etc.

2) I would make sure that you are only turning focus on for one element on the screen. Not sure what would happen if you told it to focus on more than one element... so check and make sure you're only focusing one element with one indicator.

3) If all else fails, it might be a bug in PUI. I know we've made some changes related to this not too long ago, so in that case, I would generate a JSON dump of the screen (Ctrl-F9) and send it to support. They should be able to reproduce the problem with your JSON and troubleshoot it.

1) Yes, the indicators I was using came through the conversion successfully. If they hadn't, then the first situation I mentioned would be failing, too.

2) I believe that I might have more than one of these indicators turned on at a time and, if so, it is because this is how it was done in the green-screen application. In any case, it works fine in the first situation I mentioned. It only fails in the second situation even though the same indicators are in use in both cases.

3) OK, sending information to support in a few minutes. Thanks.