Re: some comments on ddd-3.4.0

Hi Paulo --

So that we can track your suggestions and make sure that they
are not lost, please use the bug tracker:
https://savannah.gnu.org/bugs/?group=ddd

When reporting a problem, please include a test case which shows
the reported issue, including all files and commands needed to reproduce 
the problem.

See:  https://www.browserstack.com/guide/how-to-write-a-bug-report

On 7/12/24 01:52, Paulo Nogueira wrote:
> 
> 
>   Hello,
> 
>   This e-mail includes some suggestions regarding DDD, and a
>   report of some problems experienced with ddd-3.4.0 installed
>   on Fedora 37 and run on binaries produced by GFortran. The
>   suggestions first:
> 
>    1. allowing some small number of sub-programs (functions
>     and subroutines, in Fortran) to have their own Data
>     window; in that way, variables from different subroutines
>     (with the same name, say) wouldn't get mixed up with one
>     another;
> 
>    2. on current higher resolution displays the scrolling bars
>     are a bit too slim, and the scrolling bit can become tiny
>     if the source file is large; perhaps its minimum height
>     could be set at about half the font size used in the
>     respective window?
> 
>    3. the height of the usable area of the Console window
>     seems to have an upper bound (in pixels?) -- couldn't that
>     be increased (as it was done for the Data window), so that
>     the console size could be increased effectively? (the
>     window can be enlarged, but the non-gridded, grey lower
>     part is unusable).
> 
> 
>   Now the problems (already noticed with ddd-3.11):
> 
>   1. the number of breakpoint signs may _double_ after each
>    restart (multiple signs will be displayed for each line,
>    possibly until ddd "runs out" of such signs);
> 
>   2. the number of boxes in the data window can also double
>    after each restart, with the same variable being assigned
>    multiple overlapping boxes;
> 
>   3. DDD displays
>        "No symbol "xyz" in current context."
>    for variables (parameters) defined in some module that the
>    subroutine uses, instead of displaying (or printing) the
>    value of that variable.
> 
>   Kind regards
>    Paulo Nogueira
> 
> 
> 

-- 
Michael Eager