Project

General

Profile

Activity

From 06/29/2019 to 07/28/2019

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... Greg Shah
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... Adrian Lungu

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...
Greg Shah
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... Adrian Lungu

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 ... Hynek Cihlar
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. Adrian Lungu
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... Greg Shah
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...
Greg Shah

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. Greg Shah
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. Greg Shah
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.
...
Greg Shah
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... Alexei Kaigorodov
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...
Greg Shah
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... Greg Shah
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... Alexei Kaigorodov

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... Alexei Kaigorodov

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...
Greg Shah
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:
...
Alexei Kaigorodov

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(...
Greg Shah
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 ...
Alexei Kaigorodov

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 ... Greg Shah
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 "...
Alexei Kaigorodov
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...
Greg Shah
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.
Alexei Kaigorodov
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? Greg Shah
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...
Alexei Kaigorodov
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... Greg Shah
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...
Alexei Kaigorodov
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.
...
Greg Shah
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...
Alexei Kaigorodov

07/08/2019

03:46 PM Bug #3691: literal $ character in format appears on the right side of the fill-in
> They work while the window is initialized bot does not work when I edit the content of the fields.
Please explai...
Greg Shah
08:59 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
Greg Shah wrote:
> You can look inside @FillIn@ and @FillInGuiImpl@ to see how they are used.
Set a lot of brea...
Alexei Kaigorodov
12:50 AM Bug #4130: FWD truncates decimal part instead of rounding when displaying
Greg Shah wrote:
> 3. Each file that is changed needs a history entry.
Done.
Alexei Kaigorodov
12:06 AM Bug #4130: FWD truncates decimal part instead of rounding when displaying
Greg Shah wrote:
> Code Review Task Branch 4130a Revision 11322
>
> 1. Please explain the logic behind your chan...
Alexei Kaigorodov

07/07/2019

10:10 PM Bug #4130: FWD truncates decimal part instead of rounding when displaying
Greg Shah wrote:
> 2. Running the ChUI regression testing can be used as a reality check.
How to run regression tes...
Alexei Kaigorodov

07/05/2019

09:43 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
> Where in the FWD code is alignment chosen to place @screen-value@ attribute at the screen?
This was mentioned in...
Greg Shah
06:23 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
I have a question (see #3691-107).
The @dialog.p@ contains @roomRate2:screen-value = roomRate:screen-value.@. But ...
Alexei Kaigorodov
08:33 AM Bug #4130: FWD truncates decimal part instead of rounding when displaying
Code Review Task Branch 4130a Revision 11322
1. Please explain the logic behind your change. On the surface it i...
Greg Shah
06:32 AM Bug #4130: FWD truncates decimal part instead of rounding when displaying
> But I would like to run it faster, as a junit test, using some simple wrapper:
com.goldencode.Launcher.launch(com....
Greg Shah
04:55 AM Bug #4130: FWD truncates decimal part instead of rounding when displaying
made a fix in @secure/code/p2j_repo/p2j/active/4130a/@
Now the test @uast/format_string/abl/makeCheck.p@ shows full ...
Alexei Kaigorodov
01:23 AM Bug #4130: FWD truncates decimal part instead of rounding when displaying
So I have a short (1 line) 4gl test program:
@display string(DECIMAL("-99.876"), "->>>.") skip.@
I converted it to ...
Alexei Kaigorodov

07/04/2019

01:37 PM Bug #3691: literal $ character in format appears on the right side of the fill-in
My previous comments:
*the 4GL reference for "Data Types" may have something useful*
*see the NumberType and de...
Greg Shah
11:40 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
Greg Shah wrote:
> > Anyone knows where this behavior is specified?
>
> Are you asking for where the 4GL document...
Alexei Kaigorodov
11:38 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
But Eugenie's point is correct. The 4GL docs are incomplete and sometimes wrong. Greg Shah
11:37 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
> Anyone knows where this behavior is specified?
Are you asking for where the 4GL documentation explains this (the...
Greg Shah
11:36 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
Alexei Kaigorodov wrote:
> I have a question: if a decimal number has more digits after the point than the format al...
Eugenie Lyzenko
11:26 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
I have a question: if a decimal number has more digits after the point than the format allows, then 4gl rounds that n... Alexei Kaigorodov
11:01 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
> I could not found the rules which govern such alignment
If you have specific questions, post them here.
> an...
Greg Shah
05:51 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
Filed a bug report #4130 "FWD truncates decimal part instead of rounding when displaying" which describes the reason ... Alexei Kaigorodov
12:02 PM Bug #4135: high dpi screens display in low dpi
A customer has reported that the web client renders in a low resolution when run using a high dpi screen (e.g. a MacB... Greg Shah
12:01 PM Bug #4135 (Test): high dpi screens display in low dpi
Greg Shah
11:58 AM Support #4134: reduce the processing for calculated columns
If FWD evaluates the expressions for a calculated browse column more than the 4GL, then we can speed things up by mat... Greg Shah
11:54 AM Support #4134 (New): reduce the processing for calculated columns
Greg Shah
01:10 AM Bug #4130: FWD truncates decimal part instead of rounding when displaying
the article [[https://knowledgebase.progress.com/articles/Article/000030560]] reads:
@FORMAT rounds the displayed ...
Alexei Kaigorodov
12:54 AM Bug #4130 (New): FWD truncates decimal part instead of rounding when displaying
Alexei Kaigorodov

07/03/2019

06:16 PM Feature #4129: map web client users to OS accounts
h2. Existing Approaches
The web client is designed with a server-driven spawning process for launching the FWD cli...
Greg Shah
04:58 PM Feature #4129 (Closed): map web client users to OS accounts
Greg Shah
09:46 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
Both drivers work. Checker shows that results on 4gl in ChUI and GUI modes are identical. FWD results in ChUI and GUI... Alexei Kaigorodov

07/01/2019

02:29 PM Bug #3889 (WIP): incorrect initial widget and screen values for combo boxes and selection lists
Adrian Lungu
10:20 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
Alexei Kaigorodov wrote:
> Greg Shah wrote:
> > To capture output from GUI and ChUI are different runs of the same ...
Greg Shah
10:05 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
Greg Shah wrote:
> To capture output from GUI and ChUI are different runs of the same capture driver, right?
Right,...
Alexei Kaigorodov
10:00 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
Alexei Kaigorodov wrote:
> Greg Shah wrote:
> > None of these plans are correct. The purpose of a driver @.p@ is t...
Greg Shah
09:51 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
Greg Shah wrote:
> None of these plans are correct. The purpose of a driver @.p@ is to run ALL of a given process.
...
Alexei Kaigorodov
08:53 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
None of these plans are correct. The purpose of a driver @.p@ is to run ALL of a given process. So you can create:
...
Greg Shah
08:35 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
Greg Shah wrote:
> Your current directory is @uast/format_string/bin/@
Yes
> Again, the solution here is keep y...
Alexei Kaigorodov
08:00 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
Your current directory is @uast/format_string/bin/@ and you are opening a relative path @format_string/generated/feed... Greg Shah
07:45 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
thanks to Constantin Asofiei, running uast/clean.ch helped.
Next problem is:
following code in @format_string/bin...
Alexei Kaigorodov
07:24 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
Refactored *.p files to use names starting with @format_string@ everywhere. Checked that all they run in 4gl. However... Alexei Kaigorodov
05:40 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
> The alternative is to make the 4GL folder structure be the same as the one in FWD, and run the program via e.g. pro... Greg Shah
04:15 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
Alexei, about your issue with @include files must be relative to testcases/uast@. The problem is generated by the fa... Constantin Asofiei
11:19 PM Bug #3691: literal $ character in format appears on the right side of the fill-in
Greg Shah wrote:
> > include files must be relative to testcases/uast, not to the location of the referencing proce...
Alexei Kaigorodov
07:27 AM Bug #4126: Discrepancy in FWD runtime data
There is a script in @testcases/uast@, called @cleanup.sh@ - this script is supposed to clean all conversion artifact... Constantin Asofiei
07:15 AM Bug #4126: Discrepancy in FWD runtime data
Look at the attached screenshot: variable @definedModes@ obtained as @caller.getParameterModes(function)@ has value "... Alexei Kaigorodov
07:00 AM Bug #4126 (Closed): Discrepancy in FWD runtime data
Alexei Kaigorodov

06/30/2019

06:25 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
> include files must be relative to testcases/uast, not to the location of the referencing procedure (which is evide... Greg Shah

06/29/2019

10:28 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
Constantin Asofiei wrote:
> Alexei Kaigorodov wrote:
> > It turned out that references to external procedures and i...
Alexei Kaigorodov
10:12 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
Alexei Kaigorodov wrote:
> It turned out that references to external procedures and include files must be relative t...
Constantin Asofiei
08:29 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
It turned out that references to external procedures and include files must be relative to @testcases/uast@, not to t... Alexei Kaigorodov
 

Also available in: Atom