Set64rs-Change-from-dbgrid-to-flexGrid: Difference between revisions
| Line 50: | Line 50: | ||
>>>>currently uses PROFILENAME to set ProfileLog pointer > this risks not flagging user of erratic PRL/PRH pointers | >>>> currently uses PROFILENAME to set ProfileLog pointer > this risks not flagging user of erratic PRL/PRH pointers | ||
>>>> should use freshly read PRL/PRH ? | |||
| Line 57: | Line 57: | ||
'''SetProfilePointer''' > was setting dbgrid.row = row with name matching that recalled from configuration db table | |||
* called by: | |||
** RecallProfileExecuting | |||
>>>currently uses PROFILENAME to do the set > Should use freshly read PRL/PRH? | >>>currently uses PROFILENAME to do the set > Should use freshly read PRL/PRH? RESOLUTION: YES: now uses | ||
Revision as of 15:41, 23 June 2010
This is a sub list of Set64rs-Software-Issues
UpDateControllerConfigurationTable
- FUNCTION: updates PRL / PRH in database at bootup > checks to see if range is in ProfileLog
- called by:
- bootup in form_activation
>>>>relies on ReadRunState to read fresh values ...only does current channel at bootup form activation
>>>>should freshen up the values it stores itself rather than relying on other routines
>>>>should be called by InitializeInterface so it occurs when channel is switched
RESOLUTION: appears like might be redundant after fixes below : ELIMINATED
Daisy chain of routines badly apportioned
ChangeChannel > Sets up recordsets for given channel at bootup and upon switching channels : was name InitializeInterface
- called by:
- ProfileChannelNumberDisplay_Click > When the channel changes
- calls:
- RecallProfileExecuting
- ReadRunState
>>>>is there redundant code at bootup to do the same thing? RESOLUTION: YES: eliminated redundant data.recordset setting commands
RecallProfileExecuting > recalls profile name from config table > Sets pointer arrow in ProfileLog to match this > sets profile name display field
- called by:
- BootUp
- ChangeChannel
- StartProfileButton
- Calls:
- SetProfilePointer <<<remove from this ? > put in Initialize interface
>>>> currently uses PROFILENAME to set ProfileLog pointer > this risks not flagging user of erratic PRL/PRH pointers
>>>> should use freshly read PRL/PRH ?
SetProfilePointer > was setting dbgrid.row = row with name matching that recalled from configuration db table
- called by:
- RecallProfileExecuting
>>>currently uses PROFILENAME to do the set > Should use freshly read PRL/PRH? RESOLUTION: YES: now uses
-------------------------------------------------------------------------------
StoreProfileExecuting > Stores PROFILENAME, LOWADDRESS, HIGHADDRESS in config db
StoreProfileExecutionState > Stores mdlProgramModeNumber, CurrentSegment, SegmentTime in config db