>> It was a good design. A good vision. A good goal. It's a shame nobody came on board to help me complete it.
>Sorry to hear about having to try on your own to complete it. Water down the drain unfortunately.
Still plan to complete it. Takes planning though to do it on your own. Life crashes in. Family needs, etc. We'll see.
Here are some features I've earmarked for adding at various times:
May.07.2019 for VJr 0.70 or later
---------------------------------
AROUND()
A function that would allow a DATE, DATETIME, DATETIMEX, TIME, OR
TIMEX variables to work around an indicated time, before or after
by a default amount, but allowing an input parameter to indicate
a more relative swath.
Suggested by Rick C. Hodgin on May.01.2019 for VJr 0.70 or later.
-----
JUSTDECIMAL()
A function that retrieves the decimal portion of a number as either
an integer, or as a character string.
JUSTINTEGER()
A function that retrives the integer portion of a number as either
an integer, or as a character string.
Suggested by Rick C. Hodgin on May.07.2019 for VJr 0.70 or later.
-----
THISCODE option for function calls, allowing the current contextual
framework (including LPARAMETERS and LOCAL variables) to be inherited
by the called function.
DO xyz THISCODE
xyz().thiscode
Suggested by Rick C. Hodgin on Aug.22.2019 for VJr 0.70 or later.
-----
ProgrammaticChangeWhen()
InteractiveChangeWhen()
Adds a When() clause to only fire when the condition is true.
Allows for data input to be invalid, but the related code will
only fire when it is valid.
Suggested by Rick C. Hodgin on Oct.06.2019 for VJr 0.70 or later.Here are some for the debugger:
Jan.08.2016 -- Allow for an option play a sound upon entry/engagement of
a particular breakpoint or codepoint.
-----
Jan.13.2016 -- Two options:
#1 An option to allow a "Continue Until Another Breakpoint Is Hit" to
prevent the current breakpoint from being hit on every iteration of a
loop, for example.
#2 An augment to the Jan.08.2016 idea of playing a sound, an option
to display an image near the breakpoint line so that it can be parsed
visually rather than reading the source line.
-----
Jan.12.2016 -- An option to perform a simulated call on a function, which
has its return values and parameters updated by manual settings, with the
ability to maintain a history of values used.
Also, a new Sim-Step command like Step or StepOver, which does not actually
call the function, but simulates the call by using the manually input values.
-----
Jul.20.2017 -- Allow an option to keep the function call definition line
on the display even when the function body has scrolled beyond that line.
This will allow input parameter to be examined.
Similarly, do the same for local variables (all definitions are moved to
the top where they can be examined one-by-one.
An eye-lock icon by both, so that when clicked it remains whenever
the function is in scope.
-----
Sep.12.2017 -- Allow an option for colorized instances, so separate
processes can be debugged in separate instances, and it's immediately
intuitive which one it is by the color. Green for the main app, blue
for another, red for another, etc.
-----
Dec.20.2017 -- An option to allow a window / pane to be paused or data-
disabled to not perform any updating, to allow for either a snapshot of
some data to be viewed, or for faster single-step processing.
Snapshots can also be created and diff'd.
-----
Jun.17.2018 -- Allow for colorized current line highlighting in the
debugger, or colorized source code, based on what module you are in.
If in the base class code, blue coloring, if in module x, green coloring,
if in your own app standard syntax highlighting coloring, and if in
a 3rd-party DLL or plugin, gray scaling, or other such combinations.
-----
Jan.11.2019 -- The ability to have a single watch window expression
that takes on more than one value based on what's in context. So
often times we have lnRecno locally, and something like tnRecno in
the called function, and the same value is of interest in both lo-
cations. When one goes out of scope, the other should be displayed
unless it is out of scope. In addition, if both are in scope (the
stale version of lnRecno, and the current version of tnRecno, for
example), then there should be a way to hover over each one to see
all values input for that one watch window position.
Basically, relating the parameter used with the called function's
identifier, so it relates back to what it was in the previous frame
logically.
-----
Feb.03.2019 -- The ability to have contextual watch windows or
individual variable names within a watch window, both of which
auto-track along with program flow, letting those windows or var-
iables show up only when they are in scope.
A context button on each watch expression allows it to be married
to the current scope only.
-----
Jun.05.2019 -- Have a popup option when you hover that pins the
value shown, so that as you single-step, the value is constantly
updated after each line, and relative to the location of the place
where you moved it to when you pinned it (so multiple items can be
pinned nearby). They can be moved about on the board. Tags can
be added so they can be grouped, etc.
