That is so cool ...
Bruce
------ Original Message ------
From: "Doug Hamilton" <[email protected]>
To: [email protected]
Sent: 3/17/2020 2:38:15 PM
Subject: Re: [RBASE-L] - Tip of the Day: Friendly Naming Conventions for
Trace Debugger
This is great!
Since I probably run more code in Trace than production ;), it's really helpful
:)
Doug
Productivity Tip:
I turn TRACE ON or OFF while running a form by clicking a small hidden Enhanced
Speed Button (usually in the upper left corner of a form) that toggles DEBUG ON
and OFF; the button has no borders and is invisible until I mouse over it. At
judicious places in EEPS, I place DEBUG SET TRACE ON and have a SET TRACE OFF
before RETURN.
TRACE is OFF unless I click the button. When I click the hidden button, DEBUG
is turned on which sets TRACE ON. When I click the button a second time, it
toggles DEBUG OFF and TRACE no longer gets activated. I leave the DEBUG SET
TRACE ON statement(s) in all code and click the hidden button when I need to
trace code in a specific component.
The component ID of the invisible button is cidDeBugButton, it has a caption
indicating when Debug is on.
The following code is run in a RUN SELECT command; by using the RUN SELECT the
code is only in one place which makes for easy maintenance - like changing the
password.
--Debug EEP for all forms
SET TRACE OFF
SET VAR vDeBugPW TEXT
IF vDeBugPW <> 'dbpw' OR vDeBugPW IS NULL THEN
DIALOG 'Enter password or click Cancel to continue.' +
vDeBugPW=4 vEndKey PASSWORD +
CAPTION 'Start Debug' ICON Stop
ENDIF
IF vDeBugPW = 'dbpw' THEN
IF (CVAL('DEBUG')) = 'On' THEN
SET DEBUG OFF
PROPERTY CIDDeBugButton CAPTION ' '
ELSE
SET DEBUG ON
PROPERTY CIDDeBugButton CAPTION 'Debug On'
ENDIF
ELSE
CLEAR VAR vDeBugPW
ENDIF
SET TRACE OFF
RETURN
On 3/13/2020 10:26 AM, A. Razzak Memon wrote:
Friday, March 13, 2020
Tip of the Day: Friendly Naming Conventions for Trace Debugger
Product.......: R:BASE X.5 and R:BASE X.5 Enterprise (Version 10.5)
Build.........: 10.5.2.20312 or higher
Sections......: Trace Debugger
Keywords......: TRACE, EEP, Action, Component ID, Tabs
Did you know the Trace Debugger was enhanced with friendly naming
conventions for tabs, to better identify the module and/or source
from where the code is located?
Tracing form controls will display Component ID and Caption/Text
(if exist) and the EEP name. Code in Form Properties will display
the form name with EEP, or custom form action name. Tracing reports
and labels will display the name and the action.
The new friendly naming convention for the Trace Debugger tabs are:
. Component ID(Caption/Text)|EEP Name (if ComponentID/Caption exists)
. Form/External Form Name|EEP Name
. Form/External Form Name|Custom Form Action Name
. Report/Label Name|Action Name
. Table Name (RUN SELECT)
. Stored Procedure Name
Tracking the program flow of R:BASE applications is now much easier!
Very Best R:egards,
Razzak.
https://www.rbase.com
http://www.facebook.com/rbase/
-- For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
--- You received this message because you are subscribed to the Google Groups
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/8dcbc474-0cdd-c6bd-87ab-11aded111990%40wi.rr.com.
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/emef8cbc09-cbff-4d83-aace-2572596ee99c%40pathfinder.
