Activity
From 07/09/2019 to 08/07/2019
08/07/2019
- 02:20 PM Feature #4170 (Closed): add drag and drop support to treeview widget
- 11:24 AM Feature #3940: CREATE-RESULT-LIST-ENTRY() method support
- At this point FWD has limited implementation of @CREATE-RESULT-LIST-ENTRY@: it is only implemented for @AdaptiveQuery...
08/06/2019
- 08:20 PM Feature #4164: implement misc UI features (frame options, misc attributes)
* -test the @FRAME-COL@ function to ensure it is compatible-
* frame options
** @SCROLL@ (runtime stubs)
** -@US...- 08:17 PM Feature #4164 (WIP): implement misc UI features (frame options, misc attributes)
08/02/2019
- 12:03 PM Bug #3690: BUTTON widget reaction on SPACEBAR and ENTER keys
- I have fixed the lack of response from the buttons inside the alert box. This was due to the fact that no ActionEvent...
08/01/2019
- 02:59 PM Bug #3690: BUTTON widget reaction on SPACEBAR and ENTER keys
- Adrian Lungu wrote:
> Moved revision 11322 onto a new branch 3889a. Revisions 11320 and 11321 were merged into 4045a... - 07:12 AM Bug #4161: MESSAGE statement without data produces different output than 4GL
- There is a minor incompatibility between the @MESSAGE@ output between 4GL and FWD, at least in the case when output i...
- 07:11 AM Bug #4161 (New): MESSAGE statement without data produces different output than 4GL
07/31/2019
- 07:29 AM Bug #3690: BUTTON widget reaction on SPACEBAR and ENTER keys
- Moved revision 11322 onto a new branch 3889a. Revisions 11320 and 11321 were merged into 4045a. Branch 3690a is no lo...
07/25/2019
- 03:30 PM Bug #3889: incorrect initial widget and screen values for combo boxes and selection lists
- > I have noticed that the INT values work for the SIMPLE and DROP_DOWN combo-boxes, despite the fact that in Progress...
- 12:52 PM Bug #3889: incorrect initial widget and screen values for combo boxes and selection lists
- I made some tests onto which I ran revision 11322 of branch 3690a. By now, I have included all combo-box sub-types: D...
07/24/2019
- 10:00 AM Bug #3690: BUTTON widget reaction on SPACEBAR and ENTER keys
- I think it makes sense to split these changes. Please merge the 11320 and 11321 revisions into 4045a.
Then create... - 08:35 AM Bug #3690: BUTTON widget reaction on SPACEBAR and ENTER keys
- Indeed, revision 11321 was meant to fully fix bug #3690, while revision 11322 is still work in progress. There should...
07/23/2019
- 04:23 PM Bug #3690: BUTTON widget reaction on SPACEBAR and ENTER keys
- Code review 3690a revisions 11321 and 11322. I'm good with the changes. Just please remove the commented out code in ...
- 10:17 AM Bug #3690: BUTTON widget reaction on SPACEBAR and ENTER keys
- Yes, revision 11321 of 3690a fixes the points mentioned and it is ready for review. Last reviewed revision was 11320.
- 10:05 AM Bug #3690: BUTTON widget reaction on SPACEBAR and ENTER keys
- Adrian, do the changes in 3690a revision 11321 represent your fixes for the code review items? If so, is it ready fo...
- 10:02 AM Bug #3889: incorrect initial widget and screen values for combo boxes and selection lists
- Code Review Task Branch 3690a Revision 11322
1. For @ComboBoxWidget@, @GenericWidget@ and @GenericFrame@, we know...
07/16/2019
- 01:33 PM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Task branch 4130a was rebased from trunk rev 11326. The latest revision is now 11327.
- 12:52 PM Bug #3691: literal $ character in format appears on the right side of the fill-in
- I am going to rebase 4130a now. Do not make any changes to 4130a.
- 12:52 PM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Code Review Task Branch 4130a Revision 11321 and 11322
I've fixed the issues in items 1 and 2 as revision 11323.
... - 11:17 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- after uncommitting, branch 4130a got into inconsistent state. So I recreate all changes of the branch 4130a in the br...
- 09:44 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Code Review Task Branch 4130a Revisions 11324 and 11325
Functionally, I'm OK with trying these changes.
1. Plea... - 09:07 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- As noted previously, you MUST NOT merge changes from trunk into your branch. We have a very specific rebasing proces...
- 07:28 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- changed the fix to ArrayIndexOutOfBoundsException, now all uast/format_string tests passed. I pushed all fixes relate...
07/15/2019
- 07:55 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- I added format and data to recreate a situation when @missing>0@. This caused an @ArrayIndexOutOfBoundsException@ in...
07/12/2019
- 11:02 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- @missing > 0@ is being used to track the condition where all of the following are true:
* the result must be right... - 08:35 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Greg Shah wrote:
> Please fix it as well. Use 4130a as the branch.
I found the reason of the wrong alignment:
...
07/11/2019
- 10:22 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- > I discovered that so called floating-decimal display format in string mode works different in FWD and 4gl:
string(... - 12:52 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Greg Shah wrote:
> I am OK with trying the change from @splitFormat@ to @rightAligned@. You can put it into branch ...
07/09/2019
- 02:10 PM Bug #3691: literal $ character in format appears on the right side of the fill-in
- I am OK with trying the change from @splitFormat@ to @rightAligned@. You can put it into branch 4130a. Does it fix ...
- 11:42 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Greg Shah wrote:
> Yes, you are looking at the wrong process. As noted in #3691-67:
>
> > As discussed in the "... - 09:42 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Yes, you are looking at the wrong process. As noted in #3691-67:
> As discussed in the "Runtime Architecture":/p... - 09:37 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Greg Shah wrote:
> No. Are you debugging the FWD client?
I an debugging the FWD server. - 09:35 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- No. Are you debugging the FWD client?
- 09:27 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Greg Shah wrote:
> Set breakpoints in @FillIn.processKeyEvent()@ and @FillIn.draw()@. Then follow the event process... - 09:22 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Set breakpoints in @FillIn.processKeyEvent()@ and @FillIn.draw()@. Then follow the event processing flow through the...
- 09:08 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Greg Shah wrote:
> Look deeper that this set of classes. Look at @DisplayFormat.Presentation@.
I set breakpoin... - 05:28 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- > Debugger stops at these breakpoints when the window is prepared, but does not stops when I edit the input fields.
... - 02:55 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Greg Shah wrote:
> > They work while the window is initialized bot does not work when I edit the content of the fiel...
Also available in: Atom