Activity
From 06/22/2019 to 07/21/2019
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...
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... - 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... - 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.
- 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...
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...
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... - 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 ... - 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... - 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.... - 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 ... - 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 ...
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... - 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... - 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.
- 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... - 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... - 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...
- 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... - 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 ...
- 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...
- 12:01 PM Bug #4135 (Test): high dpi screens display in low dpi
- 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...
- 11:54 AM Support #4134 (New): reduce the processing for calculated columns
- 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 ... - 12:54 AM Bug #4130 (New): FWD truncates decimal part instead of rounding when displaying
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... - 04:58 PM Feature #4129 (Closed): map web client users to OS accounts
- 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...
07/01/2019
- 02:29 PM Bug #3889 (WIP): incorrect initial widget and screen values for combo boxes and selection lists
- 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 ... - 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,... - 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... - 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.
... - 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:
... - 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... - 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...
- 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... - 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...
- 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...
- 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...
- 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... - 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...
- 07:15 AM Bug #4126: Discrepancy in FWD runtime data
- Look at the attached screenshot: variable @definedModes@ obtained as @caller.getParameterModes(function)@ has value "...
- 07:00 AM Bug #4126 (Closed): Discrepancy in FWD runtime data
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...
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... - 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... - 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...
06/28/2019
- 10:17 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Greg Shah wrote:
> It is important that you figure it out so that you can do this in the future as needed. The @def... - 03:15 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- It is important that you figure it out so that you can do this in the future as needed. The @def frame@ can be at th...
06/27/2019
- 07:56 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Greg Shah wrote:
> > Is it possible to convert it to a function with single parameter which returns string?
>
> Y... - 03:06 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Driver reworked to avoid Extent statement. Now the code compiles but fails at runtime because it cannot find external...
06/26/2019
- 05:36 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- > Should I file a bug report?
Sure. For now, you will have to just rework the code to avoid the issue. - 05:16 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Greg Shah wrote:
> * Is the Java class (@com.goldencode.testcases.format_string.driver_dec.TestDec.class@) in the ... - 05:02 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- > pop-ups a window with the error message and waits until user clicks a button.
> I believe our goal is to make huge... - 04:46 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Greg Shah wrote:
> > I do use streams to named files, both for reading and writing.
>
> Then drop the @-b@ from y... - 04:41 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- > But the file exists:
> avk@msi-leop:~/Bugfix/3691/testcases/uast/format_string/testIfwd$ ls l /home/avk/Bugfix/369... - 04:32 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- > I do use streams to named files, both for reading and writing.
Then drop the @-b@ from your 4GL command line. I... - 04:16 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Greg Shah wrote:
> Are you trying to execute a converted program using the @client:cmd-line-option:startup-procedure... - 02:33 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Greg Shah wrote:
> When executing on different systems there will be different paths and configurations. Why not ... - 02:07 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- > So we need 2 different programs: one takes results and the other takes and compare.
OK.
You may want to use O... - 11:55 PM Bug #3691: literal $ character in format appears on the right side of the fill-in
- > To simply execute the driver user has to call a command like
>
> C:\Progress\OE116_64\bin\prowin.exe -p driver.p ... - 11:08 PM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Greg Shah wrote:
> Make one 4GL program that calls the others. Minimize parameters and make it run as simply as p...
06/25/2019
- 04:51 PM Bug #3691: literal $ character in format appears on the right side of the fill-in
- > I created a prototype 4gl driver in new directory testcases/uast/format_string/driver.
It consists of 2 programs: ... - 04:37 PM Bug #3691: literal $ character in format appears on the right side of the fill-in
- > You cannot define streams inside an internal procedure. (3359)
>
> Can you please advise how to get rid of this e... - 07:35 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Greg Shah wrote:
> Alexei: I prefer if you have a single 4GL "driver" program that runs any other 4GL code and captu...
06/24/2019
- 10:32 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Greg Shah wrote:
> Eugenie Lyzenko wrote:
> > Alexei Kaigorodov wrote:
> > > ...
> > > All additions are pushed u... - 10:19 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Eugenie Lyzenko wrote:
> Alexei Kaigorodov wrote:
> > ...
> > All additions are pushed up as revision 1875 in tesc... - 10:15 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Eugenie Lyzenko wrote:
> Again, I need a list of the Progress 4GL source files to test. I see 2 @*.p@ files in @form... - 10:13 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- > When talking about 4GL/FWD (in)compatibility, the first observation is that FWD lacks that handy commands as _progr...
- 09:59 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Alexei Kaigorodov wrote:
> The testcases themselves are written in ABL, so must be able to run on any 4gl implementa... - 09:40 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- The testcases themselves are written in ABL, so must be able to run on any 4gl implementation.
I also prepared simpl... - 09:31 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- Alexei Kaigorodov wrote:
> ...
> All additions are pushed up as revision 1875 in tescases project.
Are the testc... - 09:01 AM Bug #3691: literal $ character in format appears on the right side of the fill-in
- When talking about 4GL/FWD (in)compatibility, the first observation is that FWD lacks that handy commands as @_progr...
Also available in: Atom