FWD » Core Development » User Interface

06/15/2024

06:31 PM Bug #7657: 8-bit character entry problem in ChUI

Fixed the output in wide char mode issue. So now we have at least Euro sign in @ChUI@ terminal session. Also all Cyri... Eugenie Lyzenko

09:50 PM Bug #7657: 8-bit character entry problem in ChUI

The @7657a@ rebased with recent trunk @15284@, new revision is @15286@. Eugenie Lyzenko

06/14/2024

06:16 PM Bug #7657: 8-bit character entry problem in ChUI

Another question. Do we really need to support @UTF-8@ for interactive *ChUI* client? I see in a Progress DOC only @G... Eugenie Lyzenko

03:30 PM Bug #7657: 8-bit character entry problem in ChUI

Robert Jensen wrote:
> We @<company_name>@ support customers all over the world. 255 characters are not enough.
>
... Eugenie Lyzenko

03:11 PM Bug #7657: 8-bit character entry problem in ChUI

We @<company_name>@ support customers all over the world. 255 characters are not enough.
But for now, the current ... Robert Jensen

02:38 PM Bug #7657: 8-bit character entry problem in ChUI

The @UTF-8@ config issue resolved. So the note #7657-35 can be dropped.
The other issue here is the input handling... Eugenie Lyzenko

09:07 AM Bug #7657: 8-bit character entry problem in ChUI

What I have done in the past is put various characters into MAriaDB, then display them. The encoding is UTF-8.
1) 8 ... Robert Jensen

08:38 AM Bug #7657: 8-bit character entry problem in ChUI

The addition issue here is not clear how to set up @UTF-8@ as @cpinternal@ or @charset@. I have tried 3 ways:
1. @di... Eugenie Lyzenko

06/13/2024

06:39 PM Bug #7657: 8-bit character entry problem in ChUI

Robert,
Currently I'm working on the Java part for @UTF-8@ support in @ChUI@. And I need some assistance.
The c... Eugenie Lyzenko

08:54 PM Bug #7657: 8-bit character entry problem in ChUI

The @7657a@ rebased with recent trunk @15277@, updated to revision @15282@.
With this change the flag to use wide ... Eugenie Lyzenko

09:26 AM Bug #8872: WAIT-FOR with FOCUS explicitly specified: NO-APPLY return from ENTRY trigger must be i...

You might as well resolve it here. Greg Shah

09:17 AM Bug #8872: WAIT-FOR with FOCUS explicitly specified: NO-APPLY return from ENTRY trigger must be i...

Greg Shah wrote:
> Is this seen in customer code?
>
> > the focus is set to @focusable2@
>
I do not know.
>... Vladimir Tsichevski

09:15 AM Bug #8872: WAIT-FOR with FOCUS explicitly specified: NO-APPLY return from ENTRY trigger must be i...

Is this seen in customer code?
> the focus is set to @focusable2@
Are you referring to the @FOCUS@ system handle? Greg Shah

09:08 AM Bug #8872: WAIT-FOR with FOCUS explicitly specified: NO-APPLY return from ENTRY trigger must be i...

Other difference, which can be seen after the main issue fixed:
# OE: before the @ENTRY@ is sent to the @focusable... Vladimir Tsichevski

09:03 AM Bug #8872 (WIP): WAIT-FOR with FOCUS explicitly specified: NO-APPLY return from ENTRY trigger mus...

The following change fixes this very issue:... Vladimir Tsichevski

06/12/2024

04:26 PM Bug #8872: WAIT-FOR with FOCUS explicitly specified: NO-APPLY return from ENTRY trigger must be i...

The @WAIT-FOR@ statement can include the @FOCUS@ option. The initial focus must be set to the widget, specified as th... Vladimir Tsichevski

04:16 PM Bug #8872 (WIP): WAIT-FOR with FOCUS explicitly specified: NO-APPLY return from ENTRY trigger mus...

Vladimir Tsichevski

11:58 AM Bug #7684 (Closed): ENTRY event is emitted twice

Stanislav Lomany

11:57 AM Bug #7684 (Internal Test): ENTRY event is emitted twice

Yes, looks like it is fixed. Stanislav Lomany

09:02 AM Bug #7684 (Feedback): ENTRY event is emitted twice

Stanislav,
I cannot reproduce the problem you describe. Switching focus to @st2@ with TAB or mouse click generates... Vladimir Tsichevski

06/11/2024

06:32 PM Bug #8673: Deduce the logic behind OE focus management and implement in FWD

A strange thing in OE.
The test application:
# Defines a frame @outerFrame@ with a button @focusable4@.
# The ... Vladimir Tsichevski

06/10/2024

04:30 AM Bug #8586: Fields are not in FIELD-GROUP until they are enabled

Alexandru Lungu wrote:
> Vladimir, are the changes in 8586a going to fix #8068 as well. If so, what testing do you t... Vladimir Tsichevski

03:22 AM Bug #8586: Fields are not in FIELD-GROUP until they are enabled

Vladimir, are the changes in 8586a going to fix #8068 as well. If so, what testing do you think are required for this? Alexandru Lungu

05/30/2024

12:03 PM Bug #8586 (Internal Test): Fields are not in FIELD-GROUP until they are enabled

8586a revision 15256,
Nice simplification of @nextTabItem@!
The changes also affect other use cases like @ENABL... Hynek Cihlar

08:02 AM Bug #8586: Fields are not in FIELD-GROUP until they are enabled

Hynek: Please review. Greg Shah

05/29/2024

04:11 PM Bug #8586 (Review): Fields are not in FIELD-GROUP until they are enabled

I fixed the @private FieldGroup.nextTabItem()@ in similar way.
Now the complete tab ring can be traversed from 4gl f... Vladimir Tsichevski

10:44 AM Bug #8586 (WIP): Fields are not in FIELD-GROUP until they are enabled

The problem seems to be in @FieldGroup.getExtremeTabItem()@ method, where only *realized* items are selected:... Vladimir Tsichevski

05/27/2024

04:03 PM Bug #8809 (Internal Test): Incorrect next enabled widget calculation

Code review 8809a. The changes look good, but it will require good amount of regression testing, including ChUI regre... Hynek Cihlar

03:32 PM Bug #8809: Incorrect next enabled widget calculation

Hynek: Please review. Greg Shah

03:26 PM Bug #8809: Incorrect next enabled widget calculation

The (incomplete) fix for #8770 reverted in 8809a in rev. 15241. Vladimir Tsichevski

07:49 AM Bug #8809 (Review): Incorrect next enabled widget calculation

Vladimir Tsichevski

07:48 AM Bug #8809 (WIP): Incorrect next enabled widget calculation

Fixed in 8809a rev. 15240. Please, review. Vladimir Tsichevski

03:25 PM Bug #8770: ENTRY event is not sent for a frame when window receives focus

The (incomplete) fix moved from 8809a to in 8770a rev. 15242. Vladimir Tsichevski

09:54 AM Bug #8770 (WIP): ENTRY event is not sent for a frame when window receives focus

The following code in @TC.waitForWorker@ was probably intended to send @ENTRY@ to the frame in question, but, at leas... Vladimir Tsichevski

07:48 AM Bug #8770 (Review): ENTRY event is not sent for a frame when window receives focus

Vladimir Tsichevski

07:48 AM Bug #8770 (WIP): ENTRY event is not sent for a frame when window receives focus

Fixed in 8809a rev. 15240. Vladimir Tsichevski

06:37 AM Bug #8012: Fix combo-box corner cases

Hynek Cihlar wrote:
> Radu Apetrii wrote:
> > My opinion is that we should stick with @append@ (a.k.a. not removing... Radu Apetrii

06:30 AM Bug #8012 (Internal Test): Fix combo-box corner cases

Radu Apetrii wrote:
> My opinion is that we should stick with @append@ (a.k.a. not removing it), but I am open to ot... Hynek Cihlar

05:29 AM Bug #8012: Fix combo-box corner cases

I've followed the leads and reached multiple roots of setting @newAddedItems@. All of them pass as a parameter the va... Radu Apetrii

05/24/2024

02:45 PM Bug #8012: Fix combo-box corner cases

Radu Apetrii wrote:
> Do you have another suggestion other than seeing who added the @newAddedItems@ code and checki... Hynek Cihlar

12:06 PM Bug #8012: Fix combo-box corner cases

Hynek Cihlar wrote:
> Radu Apetrii wrote:
> > Hynek Cihlar wrote:
> > * @newAddedItems@ is correctly @null@, then ... Radu Apetrii

11:36 AM Bug #8012: Fix combo-box corner cases

Radu Apetrii wrote:
> Hynek Cihlar wrote:
> * @newAddedItems@ is correctly @null@, then the answer to the question ... Hynek Cihlar

11:09 AM Bug #8012: Fix combo-box corner cases

Hynek Cihlar wrote:
> For the added @append@ parameter, could we deduce new items are being added from the @newAdded... Radu Apetrii

05/23/2024

04:56 PM Bug #8809: Incorrect next enabled widget calculation

Run the @8809.p@ example.
In OE, the @focusable7@ button receives focus.
In FWD no focus is set.
The issue ori... Vladimir Tsichevski

03:59 PM Bug #8809 (Closed): Incorrect next enabled widget calculation

Vladimir Tsichevski

09:17 AM Bug #8807: A trigger of ANYWHERE type does not shadow existing trigger for the same event

This issue was first reported in #8606-44. Vladimir Tsichevski

09:16 AM Bug #8807: A trigger of ANYWHERE type does not shadow existing trigger for the same event

Code example:... Vladimir Tsichevski

08:54 AM Bug #8807 (Review): A trigger of ANYWHERE type does not shadow existing trigger for the same event

Vladimir Tsichevski

05/22/2024

07:14 AM Bug #8012: Fix combo-box corner cases

Alexandru Lungu wrote:
> Radu, please look into [[p2j:4GL_Unit_Testing]] and [[p2j:Writing_4GL_Testcases]], more exa... Marian Edu

07:09 AM Bug #8012: Fix combo-box corner cases

Radu, please look into [[p2j:4GL_Unit_Testing]] and [[p2j:Writing_4GL_Testcases]], more exactly into what we call "xf... Alexandru Lungu

03:08 AM Bug #8012: Fix combo-box corner cases

Code review 7806b. The changes are pretty dense so it is hard to follow every case, but they look OK to me.
For th... Hynek Cihlar

05/21/2024

11:44 AM Bug #8012: Fix combo-box corner cases

Hynek: Please review. Greg Shah

10:10 AM Bug #8012 (Review): Fix combo-box corner cases

Check the 7806b changes: Done.
Check that the 34 tests that I've created pass: Done.
Status: waiting for review.
... Radu Apetrii

08:37 AM Bug #8012: Fix combo-box corner cases

Yes, let's move ahead with 7806b and further changes can go in another branch. Please set the %Done of this task acc... Greg Shah

08:34 AM Bug #8012: Fix combo-box corner cases

Greg, the branch 7806b solves the issue on #8407. The problem (?) is that this branch contains multiple fixes for com... Radu Apetrii

07:39 AM Bug #8012: Fix combo-box corner cases

I rebased 7806b with trunk rev. 15226. I suggest waiting for the #8407 result before we decide what to do with 7806b. Radu Apetrii