Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incrementation bug #40

Open
cdgls opened this issue May 2, 2016 · 6 comments
Open

Incrementation bug #40

cdgls opened this issue May 2, 2016 · 6 comments
Labels

Comments

@cdgls
Copy link

cdgls commented May 2, 2016

When making a change in a unprojected view (ie not the highest projection), the displayed picture is not incrementing to the result of the change you made, so it looks as though nothing is happening. (Ie a new slice is created, but the picture doesn't display the newly created slice.)

@jamievicary
Copy link
Owner

Yeah, I agree this is really annoying, thanks for listing it as a bug.
On 2 May 2016 4:04 p.m., "cdgls" notifications@github.com wrote:

When making a change in a unprojected view (ie not the highest
projection), the displayed picture is not incrementing to the result of the
change you made, so it looks as though nothing is happening. (Ie a new
slice is created, but the picture doesn't display the newly created slice.)


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#40

@cdgls
Copy link
Author

cdgls commented May 2, 2016

Just to be clear, it is incrementing the first slice number, but not the second, and that's the bug --- it should increment the second as well.

@jamievicary
Copy link
Owner

I think that whatever slice or projection you're in, after making a move
with the mouse, you should be shown the slice in which the 'ordinary
effect' of that move is visible - do you agree?
On 2 May 2016 4:11 p.m., "cdgls" notifications@github.com wrote:

Just to be clear, it is incrementing the first slice number, but not the
second, and that's the bug --- it should increment the second as well.


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#40 (comment)

@cdgls
Copy link
Author

cdgls commented May 2, 2016

I think I agree, though I'm not sure what distinction is being made by 'ordinary effect' --- do you mean the effect that would be visible at that slice/projection currently on view?

@jamievicary
Copy link
Owner

I mean the effect you would see if the diagram you were looking at was
completely unsliced (ie if you clicked restrict before doing the move.)
On 2 May 2016 4:34 p.m., "cdgls" notifications@github.com wrote:

I think I agree, though I'm not sure what distinction is being made by
'ordinary effect' --- do you mean the effect that would be visible at that
slice/projection currently on view?


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#40 (comment)

@cdgls
Copy link
Author

cdgls commented May 2, 2016

Then yes, I agree.

@jamievicary jamievicary added the bug label May 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants