## 2026-08aug-19
## twice-as-slow-every-time.py
## Scribus 1.6.6 script
##

import sys
import gc

## -- for debug time
import time
from datetime import datetime


try:
    import scribus
except ImportError:
    print('This script must be run from inside Scribus')
    sys.exit()



def main():


    now = datetime.now()
    print("- BEGIN:", now.strftime("%Y-%m-%d %H:%M:%S") )
    DEBUG_start = time.time()


    scribus.setRedraw(False)


    ## -- remove textframe if they exist
    for tmp_num in range(1, 20):
        if scribus.objectExists('_textframe_'+str(tmp_num)):
            scribus.deleteObject('_textframe_'+str(tmp_num))
            print("- removed existing textframe number:", tmp_num)


    ## -- create textframe
    for y in range(1, 20):
        offset_y = y*10;
        scribus.createText(20, 4 + offset_y, 90, 6, '_textframe_'+str(y))
        scribus.setText('Text'+str(y), '_textframe_'+str(y))
        #scribus.insertText(str(y), -1)
        #print(y)

    scribus.setRedraw(True)


    now2 = datetime.now()
    print("- END:", now2.strftime("%Y-%m-%d %H:%M:%S") )
    DEBUG_end = time.time()
    print("- Execution time [seconds]: ", DEBUG_end - DEBUG_start)





if __name__ == "__main__":
    main()

    ## Explicitly force Python garbage collection at the end of the run
    gc.collect()  ## does not help, scrpit slows down two times every tine it gets called again

• Can we make the Undo system faster? Can the attached script help spotting where it might be slow?
  
• Can this slowness also affect the normal editing? Other types of automations (multiple duplicate with linking of text?)
  
• Would there be a way to avoid the slowness by, as an example, committing all the changes as one single undo (by adding a scripter command that starts and stops the undo step collecting the sub undo steps)?