Skip to content

Add the concept of priorities to TSMessages#103

Open
srekke wants to merge 2 commits into
KrauseFx:masterfrom
srekke:master
Open

Add the concept of priorities to TSMessages#103
srekke wants to merge 2 commits into
KrauseFx:masterfrom
srekke:master

Conversation

@srekke
Copy link
Copy Markdown
Contributor

@srekke srekke commented Feb 7, 2014

  • Messages are presented in order of their priority
  • This happens by sorting the messages list just before "fading in" a new message
  • If there are no differences in priority, the order stays the same

One does not need to use this new functionality; calling the original initialization methods without a priority will result in a normal priority. Note that previously a fadeOut always removed the first object in messages. I've changed this to always remove the object being faded (which should be the first). This is not essential to the new feature, but I thought it made sense with these changes.


Hi Felix,
This is something I did for my own project that uses TSMessages. Care to have a look and let me know if you think it's worth to merge this?

Thanks!
Steven

- Messages are presented in order of their priority
- This happens by sorting the messages list just before "fading in" a new message
- If there are no differences in priority, the order stays the same
@KrauseFx
Copy link
Copy Markdown
Owner

KrauseFx commented Feb 7, 2014

This looks amazing! I'll take a look and test it! 👍

@srekke
Copy link
Copy Markdown
Contributor Author

srekke commented Feb 11, 2014

I just noticed that I accidentally included the NSCopying additions I made to this pull request. They are a requirement for another (but related) feature I am working on. If you want, I could create a separate pull request for it?

@KrauseFx KrauseFx mentioned this pull request Feb 22, 2014
@KrauseFx KrauseFx added this to the 1.0 milestone Feb 22, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants