Jump to content

Please read the Forum Rules before posting.

Photo
- - - - -

Editing .DCTX files in ToolTip Tool


  • Please log in to reply
17 replies to this topic

#11 BH.

BH.

    Utility Developer

  • Contributors
  • PipPipPipPipPip
  • 1,244 posts
  • LocationCalifornia
Offline

Posted 10 March 2015 - 05:46 PM

Just an FYI - I'm am able to read the file now, but there are some missing entries.  That will take some time to debug...  Short on time today...



#12 BH.

BH.

    Utility Developer

  • Contributors
  • PipPipPipPipPip
  • 1,244 posts
  • LocationCalifornia
Offline

Posted 10 March 2015 - 09:12 PM

I have the problems fixed.  It was my code, it was a memory issue gone wild.  It would only manifest itself in large DCTX projects when reading them.  I have added a chunked version.  This should be solved, for both single block and chunked reads of DCTX modules.  The chunked mode is new and much slooooower. 

 

Do note, that many of the reading functions have a "debug" mode where the first x (usually 100) records will be read into Tooltip TNT.  Activate debug mode from the File+Debug menu.  This is good for testing purposes. 

 

I'll try to post an update to Tooltip TNT later tonight.

 

BH



#13 BH.

BH.

    Utility Developer

  • Contributors
  • PipPipPipPipPip
  • 1,244 posts
  • LocationCalifornia
Offline

Posted 10 March 2015 - 09:53 PM

========================================
Version 2.55 3/1/2015
========================================
-- Fixed - Read DCTX files would fail with a MEMORY ERROR.  Also added option to read DCTX files chunked.



#14 JPG

JPG

    Jon.

  • Moderators
  • 1,675 posts
Online

Posted 11 March 2015 - 03:16 AM

I get this error with the normal mode.

 

Report the following:
MEMORY ERROR: Insufficient Windows memory
TxSelRtfU[17]     ret←obj ⎕wi 'LoadFromMemory' arg 5 1 
                          ^
----------------------------------------
TxSelRtfU[17] *                         
TxAddRtfU[3]                            
DGenRead[79]                            
>[fmTxCtrl.mModules.mDctx.mRead;Click]  
<[fmTxCtrl;Wait]                        
Start[70]                               

 

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

 

second error that pops up after that is.

 

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

Report the following:
VALUE ERROR
TxAddRtfU[3] sink←TxSelRtfU obj arg 
                  ^
----------------------------------------
TxAddRtfU[3] *                          
DGenRead[79]                            
>[fmTxCtrl.mModules.mDctx.mRead;Click]  
 
 
<[fmTxCtrl;Wait]                        
Start[70]    
 
--------------------------------------------------------------------------------------------------
 
Reading in chunked mode was ok, but it was altogether unresponsive in scrolling and selecting text.
 
 
Jon

 


Edited by JPG, 11 March 2015 - 03:50 AM.


#15 BH.

BH.

    Utility Developer

  • Contributors
  • PipPipPipPipPip
  • 1,244 posts
  • LocationCalifornia
Offline

Posted 11 March 2015 - 12:31 PM

 
--------------------------------------------------------------------------------------------------
 
Reading in chunked mode was ok, but it was altogether unresponsive in scrolling and selecting text.  

Yes, while it is running it will be slow.  And yes, after it loads, it will be slow.  I have said and still hold that file size should be 7-10 mb max.  Large modules should be built in pieces then put together for a final release.  This is because of the text display engine just does not handle huge files.  The file in question is 100mb.  It would be best to break the file into smaller pieces. 

 

In the module in question, just the "C" entries produces an RTF file of 22mb in size.  And to just read the RTF out of the text display engine, takes 27.2 seconds on my old laptop computer.  That is time just to take the text out of the display engine for storage, no processing of data.  Read read from the DCTX file, just the "C" entries, takes 1 minute read as a single block.  Chunked would be much longer.    Reading the entire file is not advisable.  The original is posted by Josh, and I'll bet he built it in small parts and then put it all together in the end.  Note, Tooltip TNT can put the parts together and do it quickly showing that my code can handle that about of data.  The bottle neck is the text display engine, and there is nothing I can really do about that except to say, build using small parts.

 

Ideally, when editing a large file like this, a tool that can work a record at a time would be used.  Tooltip TNT is not such a tool.  It is a tool to author whole modules.  And as such, it also works on large chunks when editing data.  I have started several times to create a record editing tool, but it just is not something high on my list of things to do as I personally do not need such a tool very often.  And when I do, I use program such as SQLite Browser to access a single record and edit it. 



#16 APsit190

APsit190

    e-Sword Tools Developer

  • Members (T)
  • PipPipPipPipPip
  • 2,868 posts
  • LocationLand of the Long White Cloud (AKA New Zealand)
Offline

Posted 11 March 2015 - 03:57 PM


Ideally, when editing a large file like this, a tool that can work a record at a time would be used.  Tooltip TNT is not such a tool.  It is a tool to author whole modules.  And as such, it also works on large chunks when editing data.  I have started several times to create a record editing tool, but it just is not something high on my list of things to do as I personally do not need such a tool very often.  And when I do, I use program such as SQLite Browser to access a single record and edit it. 

 

Hi Brent,

That's the way to go, bro. And I totally agree. Makes a lot of common sense.

 

Blessings,

Autograph.png

Edited by APsit190, 11 March 2015 - 04:01 PM.

X (formerly Twitter)

 


#17 BH.

BH.

    Utility Developer

  • Contributors
  • PipPipPipPipPip
  • 1,244 posts
  • LocationCalifornia
Offline

Posted 11 March 2015 - 06:18 PM

Hi Brent,

That's the way to go, bro. And I totally agree. Makes a lot of common sense.

 

Blessings,

But of course, one needs to know the idiosyncrasies of e-Sword's data structure such as that DCTX, BBLX, and CMTX files do not include the RTF header and one needs to know how then to apply the correct format tags to make that appearance correct.  It would still be nice to have a WYSIWYG record editor.  Using Tooltip TNT to change a modules abbreviation is like using a nuclear bomb to dig a post hole. 



#18 APsit190

APsit190

    e-Sword Tools Developer

  • Members (T)
  • PipPipPipPipPip
  • 2,868 posts
  • LocationLand of the Long White Cloud (AKA New Zealand)
Offline

Posted 12 March 2015 - 04:09 PM



But of course, one needs to know the idiosyncrasies of e-Sword's data structure such as that DCTX, BBLX, and CMTX files do not include the RTF header and one needs to know how then to apply the correct format tags to make that appearance correct.

 

Hi Brent,

In many respects I agree with you, and its there where one needs a bit of a grasp of rtf code to accomplish this. I have to admit that this actually is a bit of a learning curve to do, but then, the beaut thing is that one is learning a new skill which somewhat stretches one's mind and thinking. Mind you, I'm a real geek when it comes to doing things like this, and as such could be a real glutton for punishment.

 

On that note, if anyone wants to learn a bit about RTF (Rich Text Format) code, then this resource will be invaluable to you. Click on the link below.

Word2007RTFSpec9.pdf
Last Updated Mar 22 2023 04:05 PM

 


  It would still be nice to have a WYSIWYG record editor.

 

 

Way too easy bro, make it really hard on them so they can toughen up and endure pain, like me ... "MUUUUMMY"

 


  Using Tooltip TNT to change a modules abbreviation is like using a nuclear bomb to dig a post hole.

 

 

Or like using a 105mm or 155mm Howitzer in a firing squad to execute a prisoner. Either way, its a real blast LOL.gif

 

Blessings,

Autograph.png

X (formerly Twitter)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users




Similar Topics



Latest Blogs