libvips / libvips/nip4

Duplicated cell issue. (on hold)

Open
#27 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
98
Forks
4
Avg merge
21m
Merged PRs (30d)
1

Description

Something inherited from nip2.
Looked if I could find anything related in nip2 and nip4 (Issues & TODO) but did not find anything seemingly related.
Thought I had read or wrote something about it (before nip4 came around), but apparently not.
As it seems to have never been reported. I fear its just one other very specific local nip* problem.

The general issue with copies of duplicated cells is that they don't stick to any setting changes that are made to them.
Initially the cell-copy seems to work ok with the new settings. But when they are auto-recalculated (when something was changed in there input source/path) they flip back to displaying & using there default values.

So far the only way to get those cell-copies to work normally again it to change the cell command (ie: inputting some nr +enter, and than restoring the initial command+enter). Which, apart from the problems they give, also kinda defeats the whole point of using the 'duplicate-cell' feature. (_not sure at this moment if saving and reloading the workspace got rid of these issue. Think I checked, but that was a long time ago/ - Yes: it did.)

Image:

  • A+C: Is both before and after B.
  • B: Opened same setting, and closed them with a ENTER.
    • Any real 'setting change' will be picked up by the cell ... but only until the next re-calculation comes along.
    • (cell A10, directly above A4 in image, was the duplicated cell. With A4 being the copy. A immediately created copy of A4 turned up with its default setting.)

Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the duplicate-cell scenario described for cells A4 and A10, changing a setting and triggering recalculation by changing the input source or path. Check whether the setting is retained after recalculation and after saving and reloading the workspace; the issue provides no file or test entry point.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.