-
Notifications
You must be signed in to change notification settings - Fork 14
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
DM-4484: Catalogs Overlay #44
Conversation
Also the following: - Introduction of Sagas - fixed TargetPanel bug - added forceReinit property to FieldGroup components - added z-index for dialogs
return; | ||
} | ||
|
||
const params= { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here you might want to specify "decimate" parameter to handle large catalogs:
decimate: serializeDecimateInfo(columns.lonCol, columns.lonCol.latCol, numPoints [,limits])
The helper function is in Decimate.js
OK, I've got basic idea of how you use sagas. Though I should say generators are mind twisting. (Hopefully, we'll get used to them.) One thing I noticed: When I bring another image and another catalog, the highlighted row is not reflected in the catalog, even though clicking on a point seems to change it. |
Once you do get your head around generators these sagas really simplify the flow. Everything become really straight forward. I am really excited about them. |
I am already working on part two of the ticket (DM-4503). I will fix the bug and add the decimate in that one. |
case DataTypes.SELECTED_IDX_ARY: | ||
return null; | ||
break; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the "break" is not needed here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
your right, in this case none of them are needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to return null or throw an exception so it can be re-thrown and trace upfront? Or do we handle the 'null' on the component view after dispatch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The way the getDrawData
is made it supports nulls. However, the next ticket (the one I am working on now) we will support selected.
canFilter: true, | ||
helpLine : helpText, | ||
canUserChangeColor: ColorChangeType.STATIC | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One improvement we should add here (or to a different ticket) is that the user should be able to change the shape and size of the overlay symbol
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would be pretty easy to do. More work in the UI than anything else.
Catalogs Overlay
Also the following: