Scenario:
I want to paste, say, 50 items as sub-items to a pre-existing item. I select an existing sub-item of the item and paste (pasting by selecting 1- Plain Text and then 2- Paste all lines into selected item(s). 49 new items will be created).
Result:
If I do the above in a regular Grid, fast.
If I do the above in a Scratch grid, where just one Scratch grid is open under IQ, fast.
If I do the above in a Scratch grid, where multiple Scratch grids are open under IQ, very slow (but it does finish, and everything is pasted properly).
This might relate to my non-supported use of Scratch grids (i.e. having multiple Scratch grids open simultaneously). But, for optimal workflow and efficiency, I usually wind up having a few Scratch grids open simultaneously (which is, to me, one of the many excellent capabilities of IQ).
Comments
Hi, I was not able to…
Hi,
I was not able to reproduce the issue. If you can reproduce it in a sample app, please send it over !
I investigated further…
I investigated further. Agreed, the problem does not appear when I first open IQ, or for days even. I finally encountered the problem after about four days into use of IQ (I tend to leave IQ open for days on end). I did not deduce an obvious trigger (going forward, I'll keep looking for a trigger). As an aside, IQ did seem to become a bit sluggish about two days into use, after I pasted 1000 items (copied from a web page in MSFT Edge) as new items in a single paste operation. This was all on V127.0Pre12. Updating to Pre13 now. I should note that closing and reopening IQ resolves everything. Thanks.
Another occurrence: Using…
Another occurrence:
Using Pre13, and the IQ app had been open for two days. I pasted 899 items (copied from a web page in MSFT Edge, pasted as new items in a single paste operation), as sub-items of an item ("Item X") that was open in a Scratch grid (note: the top-level item of this particular Scratch grid was the "grandparent" of item X). The paste appeared to start quickly but then became sluggish. And, thereafter, the issue (discussed in the first post of this thread) presented itself.
Of course, I can close and restart IQ to fix this, so not a critical problem as far as I am concerned. Just collecting data to see if a pattern/cause reveals itself. Thanks.