Skip to content
Snippets Groups Projects
Commit 39683744 authored by gb10's avatar gb10
Browse files

Fixed a bug with getting dotter coords from the current big-picture display range in protein blixem

parent c078606f
No related branches found
No related tags found
No related merge requests found
......@@ -193,9 +193,12 @@ static void onBpRangeButtonClicked(GtkWidget *button, gpointer data)
BlxViewContext *bc = blxWindowGetContext(dialogData->blxWindow);
GtkWidget *bigPicture = blxWindowGetBigPicture(dialogData->blxWindow);
const IntRange const *displayRange = bigPictureGetDisplayRange(bigPicture);
const int qStart = convertDisplayIdxToDnaIdx(displayRange->min, bc->seqType, 1, 1, bc->numFrames, bc->displayRev, &bc->refSeqRange);
const int qEnd = convertDisplayIdxToDnaIdx(displayRange->max, bc->seqType, 1, bc->numFrames, bc->numFrames, bc->displayRev, &bc->refSeqRange);
char *startString = convertIntToString(bc->displayRev ? displayRange->max : displayRange->min);
char *endString = convertIntToString(bc->displayRev ? displayRange->min : displayRange->max);
char *startString = convertIntToString(qStart);
char *endString = convertIntToString(qEnd);
gtk_entry_set_text(GTK_ENTRY(dialogData->startEntry), startString);
gtk_entry_set_text(GTK_ENTRY(dialogData->endEntry), endString);
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment