Set64rs-Change-from-dbgrid-to-flexGrid: Difference between revisions

From *** My Personal Wiki ***
Jump to navigation Jump to search
New page: == UpDateControllerConfigurationTable == *FUNCTION: updates PRL / PRH in database at bootup > checks to see if range is in ProfileLog *called by: **bootup in form_activation >>>>re...
 
No edit summary
Line 1: Line 1:
== UpDateControllerConfigurationTable ==
== UpDateControllerConfigurationTable ==


Line 15: Line 14:
>>>>should be called by InitializeInterface so it occurs when channel is switched
>>>>should be called by InitializeInterface so it occurs when channel is switched


>>>>appears like might be redundant after fixes below
RESOLUTION:  appears like might be redundant after fixes below : ELIMINATED




Line 21: Line 20:




== Daisy chain of routines badly apportioned ==


InitializeInterface > Sets up recordsets for given channel  at bootup and upon switching channels


  > called by: ProfileChannelNumberDisplay_Click > When the channel changes
'''InitializeInterface''' > Sets up recordsets for given channel at bootup and upon switching channels


  > calls:  RecallProfileExecuting
*called by:
** ProfileChannelNumberDisplay_Click > When the channel changes


  > calls:  ReadRunState
* calls:   
** RecallProfileExecuting
** ReadRunState





Revision as of 15:16, 23 June 2010

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

InitializeInterface > Sets up recordsets for given channel at bootup and upon switching channels

  • called by:
    • ProfileChannelNumberDisplay_Click > When the channel changes
  • calls:
    • RecallProfileExecuting
    • ReadRunState


>>>>is there redundant code at bootup to do the same thing?????



RecallProfileExecuting > recalls profile name from config table > Sets pointer arrow in ProfileLog to match this
                       > sets profile name display field
 > called by: BootUp
 > called by: InitializeInterface
 > called by: 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
 > only called by RecallProfileExecuting


>>>currently uses PROFILENAME to do the set > Should use freshly read PRL/PRH?







 -------------------------------------------------------------------------------


 StoreProfileExecuting > Stores PROFILENAME, LOWADDRESS, HIGHADDRESS in config db


 StoreProfileExecutionState > Stores mdlProgramModeNumber, CurrentSegment, SegmentTime in config db