You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I might be missing something major here, but I've been playing around for a few hours, and can't get anywhere. My initial composition tests worked beautifully, but some secondary tests I ran had some failures (see dankamongmen/notcurses#1990, if you'd like). At first I thought this related to moving the image being edited, but further experimentation eliminated that as a factor. Here's the minimal test case I've winnowed this down to (I've elided seemingly uninteresting arguments; all save the first command are specifying the same i= image id):
_Ga=d to clear all images -- result is expected clear screen
_Gf=32,p=1,a=t;DATA -- no result, image has only been loaded
_Ga=p,p=1 -- result is expected opaque image, as frame 1
_Ga=f,X=1,r=2,c=1;ZEROEDDATA -- no result, frame 2 has been prepared with transparent cell
_Ga=a,c=2 -- result is expected frame 2, missing transparent cell
up through here we're all good. then:
_Ga=c,r=2,c=1,C=1 -- i expect this to change frame 2, using data from frame 1 (filling back in the cell)
_Ga=a,c=2 -- i expect the change to be visible by now
but the change is not yet visible. i think that second line is a no-op, but have included it for completeness.
however, i can then do:
_Ga=f,[some other rectangle],X=1,r=2,c=2;DATA
and both this change, and the previous composition, become visible.
So sorry for missing this earlier. The test case I was running rapidly iterated over all cells of the image, erasing and then restoring them. Since each restore (save the last) was immediately followed by an erase elsewhere, everything works in that test. On more complex ones, however, I'm never seeing my restores.
This analysis might still be incomplete. It's been a perplexing few hours. I'm happy to run whatever tests you'd like.
I can attach the textfle chunks I'm using to test this, if it would be helpful.
This is with 0.22.0, and it may very well be my bug still.
The text was updated successfully, but these errors were encountered:
Describe the bug
I might be missing something major here, but I've been playing around for a few hours, and can't get anywhere. My initial composition tests worked beautifully, but some secondary tests I ran had some failures (see dankamongmen/notcurses#1990, if you'd like). At first I thought this related to moving the image being edited, but further experimentation eliminated that as a factor. Here's the minimal test case I've winnowed this down to (I've elided seemingly uninteresting arguments; all save the first command are specifying the same
i=
image id):_Ga=d
to clear all images -- result is expected clear screen_Gf=32,p=1,a=t;DATA
-- no result, image has only been loaded_Ga=p,p=1
-- result is expected opaque image, as frame 1_Ga=f,X=1,r=2,c=1;ZEROEDDATA
-- no result, frame 2 has been prepared with transparent cell_Ga=a,c=2
-- result is expected frame 2, missing transparent cellup through here we're all good. then:
_Ga=c,r=2,c=1,C=1
-- i expect this to change frame 2, using data from frame 1 (filling back in the cell)_Ga=a,c=2
-- i expect the change to be visible by nowbut the change is not yet visible. i think that second line is a no-op, but have included it for completeness.
however, i can then do:
_Ga=f,[some other rectangle],X=1,r=2,c=2;DATA
and both this change, and the previous composition, become visible.
So sorry for missing this earlier. The test case I was running rapidly iterated over all cells of the image, erasing and then restoring them. Since each restore (save the last) was immediately followed by an erase elsewhere, everything works in that test. On more complex ones, however, I'm never seeing my restores.
This analysis might still be incomplete. It's been a perplexing few hours. I'm happy to run whatever tests you'd like.
I can attach the textfle chunks I'm using to test this, if it would be helpful.
This is with 0.22.0, and it may very well be my bug still.
The text was updated successfully, but these errors were encountered: