Updated version of the SeekLine method (by optimizing the code, the search process accelerated by approx. 50%; bugs related to the record map update were removed):
- demo.zip
- (9.89 KiB) Downloaded 149 times
BTW. Interesting behavior of method and variable in class objects.
First, I read a variable from one object and write its value to a variable in another object.
Then I update the value in the second object, and to my surprise, the value in the first object also changed to take the value from the second object.
I don't know why this is happening, can someone who knows the classes well explain it to me?
You can see this effect by searching for e.g. 11222333 in incremental browsing by calling menu "File" -> Open file (without counting the number of lines) - incremental reading file.
Code snippet showing this situation:
Code: Select all
//I read aRecordsMap from the oFileGrid object and save it to the oFileMT object.
oFileMT:PutRecordsMap ( oFileGrid:GetRecordsMap() ) // <--- If I do not execute this methods before changing aRecordsMap in the oFileMT object, then in the oFileGrid object there is the original value of aRecordsMap.
//Why does this result in "::aRecordsMap" being synchronized between two different objects later in the code?
//aRecordsMap should only be updated in the oFileMT object.
lFound := oFileMT:SeekLine( AllTrim( Form_1.tb_Seek.Value ), Form_1.Grid_1.Value, .T. , { | nPos, nLastPos | Form_1.PBar.Value := nPos / nLastPos * 100 } )
//Why is aRecordsMap the same in both oFileMT and oFileGrid?
MsgInfo ( "Items in 'aRecordsMap' of 'oFileGrid' object: " + Str( Len ( oFileGrid:GetRecordsMap() ) ) + CRLF + ;
"Items in 'aRecordsMap' of 'oFileMT' object: " + Str( Len ( oFileMT:GetRecordsMap() ) ) )
. In ANSI, there is no leakage in the Grid. 
if Yes how 