Link to first unread message in a thread?

From reading some of the other threads, I see that NI is working on some upgrades and modifications to the Forums.
My suggestion is that a option be included that will take me to the first unread message in a thread. When a thread goes to several pages, it can be tricky to find the postings which I have not yet read. The >> link connects to the newest page if more pages are present than the enumerated list will display and << goes back to the beginning. The [NEW] flag is reliable, so the system knows which posts I have read. It appears to be technically feasible, but I have no idea how difficult such a navigation task would be. I am drawing a complete blank when it comes to suggestions for a symbol or title for the link. I think a symbol is preferable considering the number of languages sued by the members of the Forums.
Thanks,
Lynn

How about this?
Worked fine for years.
Try to take over the world!
Attachments:
NewPost.PNG ‏8 KB

Similar Messages

New forum feature: A button or option to jump to the first unread message in a thread.

It would be handy if we had a way to open a thread and jump to the first unread message in the thread. This is especially usual when reading very active threads and it would save us some time getting back to the point in the discussion where we left off.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

altenbach wrote:
Another variation of this would also be useful: ....
Actually, we already have that, but I tend to forget. We simply need to click on the nonzero number all the way on the left.
LabVIEW Champion . Do more with less code and in less time .

Collapsed view: how to see "most recent unread message" instead of "first unread message" in a thread in Mail

Hey all,
I use the inbuilt Mail-software on my Macbook with Lion 10.7 and I constantly overlook new messages in a thread, as I organize by conversation and usually have all my threads in 'collapsed view'. For some reason Mail seems to prefer showing the 'first', i.e. the earliest unread message as the one message that I see in collapsed. If there are newer messages already in the thread, I don't see them, unless I un-collapse the thread. I find this really unintuitive and annoying, my inbox seems far more static than it really is.
Is there any way to change this and have Mail show me the most recent unread message as the message I see in collapsed view?
I appreciate any advice.
Thanks, Carl
PS: BTW, I have the same problem on my iPhone, double props to you if you can solve it for both Mail and iPhone!

Mail
Preferences
Viewing
Check put most recent message at top

Easily reaching last message in a thread

You know messages can be mixed in threads, since anyone can answer to a intermediate message and its reply may appear in before some other posts even if it has posted after them.
Since the last thread post is noted in message listing page, it could be useful to add near that note a little icon that jumps directly to that message, wherever it is in the thread.
BTW, I don't know if it's possible to save thread options on a thread basis (i.e. permanently read some thread sorted oldest to newest and another newest to oldest and maybe another in threading order).
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

Roberto Bozzolo -
It's not possible to save thread sorting options on a per thread basis. However, you can change your view to always sort newest to oldest so the new ones are always first in the list.
In your profile, there is an option to "Automatically Jump To The First Unread Message In A Thread." This option works well when the threads are sorted newest to oldest or oldest to newest. However, it has problems finding the right message when the view is sorted by threading and the discussion spans multiple pages.
The subject of the message has [NEW] at the end of it if you haven't read it yet which is your visual indicator that it is the new message in the thread.
Long story short, I think I understand the feature you are looking for and have tried to give you some suggestions on what you can do today to accomplish it. I will add your feedback to the other requests on this topic and hope to get a better solution for you.
Thanks for the feedback!
Molly K.
Web Support & Operations Manager
National Instruments

Mail flooded with unread messages/FB app not working...linked?

All at once my Mail inbox has over 2,400 messages and Facebook app not working. I have not updated the last 2 updates bc of storage, but don't know why yesterday it decided to have a problem with that? Any ideas what's going on and how to fix it?

After Googling this issue to death, I finally clicked on the ? icon in the mail preferences panel. Apparently this is working as intended:
Display unread messages with bold font:
Display unread messages in bold font in classic layout, to help you distinguish them from messages you have read.

Since yesterday clicking on a link in an email message firefox doesn't open a new tab with that particular website.

I am using Firefox 3.6.13 on a 2009 Mac Pro computer (OSX 10.6.6). Up until yesterday when I clicked on a link in an email message Firefox opened a new tab and switched to that particular website. Since yesterday Firefox doesn't do that. I have Firefox set up as my default browser. I tried to change my default browser to Safari, then everything worked fine. Clicking on a link in a message a new tab has opened in Safari with that particular website. My problem is, that I like Firefox a bit more than Safari and I'd like to know what to do to restore that functionality to Firefox.

It's a good idea to try disabling Flash completely and see whether the problem continues. If it does, then my guess is incorrect. To test that, open this tab:
orange Firefox button (or Tools menu) > Add-ons > Plugins category
Here you can locate Shockwave Flash and use the Disable button. Keep this tab open for easy access when doing your test.
''If your test confirms that Flash is causing the problem,'' then the other thread has two suggested workarounds. The first is simple to understand (keep some Flash running at all times) but may be inconvenient to do all the time. The second is trickier because it requires editing a file in (or creating and then dragging a file into) a system folder. Fortunately you only need to do it once.

3.0+ imap Gmail Unread Message

Ever since the update to 3.0 my imap Gmail account on my iPhone shows that I have one unread message. It is blank, dated 12/31/00. I cannot open it or delete it, and it's always there. It wasn't fixed in any of the subsequent updates. I looked through Gmail threads and several people posted the same problem, but no solution. Any ideas?
I apologize if this question has already been asked, but I couldn't find it.

I found this link on Gmail site. See if it works to meet your requirements:
http://mail.google.com/support/bin/answer.py?answer=78892

Curve 8310 Unread message not there

Has anyone had their blackberry say there's an unread message but when you check all your folders there's no new mail message? I've had this notification on my phone for days now and it's driving me insane.

Hi and Welcome to the Forums!
This happens more frequently than one would hope. I find the quickest way to find it is via a search:
Homescreen > Messages > > Search
Set as follows (may vary depending on your device OS level):
Search Type: Local
Name In: Any Address Field
Subject Message: <leave blank>
Include Encrypted Messages: Yes
Service: All Services
Folder: All Folders
Show: Unopened Only
Type: All
That should return to you all unopened messages from all message conduits.
Good luck and let us know!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

How can i get my daughter's imessage on my iphone and still have it show up on her ipod as an unread message

I have my iPhone setup so I can also get all of the iMessages that my daughter sends and receives on her iPod. The problem is that if I read the message first then it doesn't show up as a new message on her iPod and therefore she doesn't know that a message was sent. Is there a way that I can get my daughter's iMessage on my iPhone and still have it show up on her iPod as an unread message? Any ideas from anyone will help. I can't figure it out

HI,
I am not sure that I can really add anything to to this.
Apple used the phrase "sync" when saying what Messages on the Mac would do in regards to showing iMessages that were going to iOS devices.
It took to OS X 10.8.2 and iOS 6 to get as close as we have right now.
At best it looks like "Sync" means "Display on all Devices" and not much more.
The Mac version implies it will do more as there is a setting to notify people by return that you have read the iMessage.
The iOS devices have a similar "Send Receipts" item in the settings.
However actually reading an iMessage on one device seems to bear very little resemblance to anything that happens or can be seen on another device.
It seems for most people reading an iMessage on one device shows nothing at all on another device (the presumption being it arrives all places at the same time)
Your post is the closest I have seen to someone suggesting that it can be different on different devices.
You also seem to be implying that there is almost a time difference it the time your iPhone gets the iMessage and the time the iPod touch gets it.
I have certainly seen the "silent arrival" of iMessages on both my iPhone (when my computer and Messages is On) and on the iPhone if the conversation started on the Mac.
The Mac end will show both "Sent" and Received sides as it "Syncs" the conversation and beeps the alert sound for the Received part and the iPhone will remain silent.
Even "talking it through" like this in this post I am not coming to any real conclusions about what to try.
I am not even sure what to suggest to test for things to look out for.
10:13 PM Monday; January 21, 2013
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 iMac 2.5Ghz 5i 2011 (Mountain Lion 10.8.2)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad
"Limit the Logs to the Bits above Binary Images."  No, Seriously

How to global remove unread message mark in Mail

I just vacated MS Outlook for Mac to use Mail for the first time. I'm running Mac OS X 10.7.4 and am current on updates. All of the messages in the folders that I moved from Outlook to Mail are marked as unread. I must have 1,000 marked messages. Is there a way that I can select a folder and then globally removed thed blue unread message mark?

Something happened and is fixed.

10.5 Mail: Hide unread message counts of folders? (or, how backup all mail)

Ok, this is a very confusing topic. I have connected Apple Care, and they understand what I'm trying to do, but say there is "no way" that it can be done. But I know there is a way so hopefully someone can help.
First, this is what I'm asking for...then I'll explain why. I am looking for a way to "hide" the unread mail counts of a SPECIFIC FOLDER. (not the in box, not all messages, ONLY messages in ONE folder.)
Here is why.... I finally got my mother using email with her Verizon DSL address in Mail.app. The problem is, she is one of those people that "deletes" just about every message she gets because she "doesn't need it anymore" But, there has been many times where she has deleted something that down the road might be needed - and therefore, it is lost. Sure, Time Machine is set up and could recover it, and there are other ways of getting things back, but is just too difficult, and those methods don't last forever.
So here is what I did to solve this and make it easy - I set up a RULE in mail.app that takes every message and COPIES it to a folder called "BACKUP." Now, she can delete things from her in box when she is done with them (which will make her happy) but down the road if the message is ever needed again, it is just a search or even a SPOTLIGHT search away! Or, you could just open the "backup" folder and see an index of ALL the messages. So I had this setup for a while and it was great....but there was one problem.... The folder "backup" would count un-read messages. So after a while, she would go to check her mail and see that she has 50 unread messages! (only 1 of which was really un-read in her in box, but the other 49 where old copies in the backup folder.) So I then edited the rule and found an action to mark the message as read. Time goes by and then I realize that NOTHING in being marked read. So even real unread messages in the in box would immediately be marked as read and would not come up as bolded or with the blue dot. So that became annoying as it was hard to see what was new and what wasn't. So then I came up with this idea of setting a rule that all of her Verizon email would be forwarded to another account (I set up a gmail account for her) so that all I messages would be forwarded there. Then, I setup gmail to forwarded them back thinking it would be easy to setup a rule that says any message coming from "gmail account" would be moved to folder and marked as read. I then get a panic phone call saying..."my inbox keeps getting hundreds of unread messages...there all the same thing! I then log in to see that one new message was being pushed back and forth between Mail.app and gmail in an endless loop! so I had to shut the forwarding to stop that!
So as you can see....this is very difficult, but yet the problem is so simple and should have an easy fix. All I want is a way to backup all incoming messages, and keep them stored in a folder that marks them as read.
Could anyone PLEASE help me out with this? _Apple says there is no way to do this because of the limitations in the Rules that mail.app provides_....but it does give me the option to run an Apple Script. _AppleCare said that it could easily be done via an Apple Script_, but I have NO CLUE on how to even start that! Even the easy tutorials I tried left me confused.
So - ANY ideas????
Thank you SO much in advance for anyone that could help out!
-Scott

Sorry I am marking this solved, but it never was.
The best thing that could be done is to rely on Time Machine, or forward all of your incoming email to another address.
Apparently, there is no way to do what I asked. But there should be. So Apple, please fix this.
Again, sorry I am marking it as solved.

To get unread messages in any folder "exactly once"

What am trying to do?
a. Poll the mail server(might be MS or gmail or yahoo..) (say now).
b. Get unread messages from a mailbox folder via IMAP. (via +'SEEN'+ flag)
c. Process the unread messages i.e. in my case i will send SMS to users according to filters specified.
d. Sleep and Poll the mail server after 10 min(say)
e. Now the question is how to do i get the next set of unread messages i.e. the unread messages other than those that i got in step (b)
Rules-
a. Note that i can't set the message as '+READ+' or '+SEEN+' as mine is not the standard client.
b. I think i can get hold of the largest message UID in the first poll and save it and in the next poll try to retrieve only the unread
messages with UID greater than that i saved. +But is there any good and easy approach to do the above+?
c. Also to be clear, in the interim period between two polls, if the user really reads a mail via his/her client, then in the next poll i am not interested in those read mails. So the question arises only if the user doesn't check any mail where my application really comes into picture
Please assist. Ping me if am unclear.

Thanks. It's working for 'IMAP'. I need it for IMAP only.

"Portable" way to do message passing between threads?

(I posted this on the Apple Developer Forums already, but since that forum is only accessible to registered and paid iPhone developers, I thought it would be nice to put it here as well so as to get some more potential eyeballs on it. I apologize if this kind of "cross-posting" is not kosher/is frowned upon around here.)
Hey everybody,
"Long-time listener, first-time caller," heh.
I've been working for the past 2-3 months on my very first iPhone app. Actually, what I've been working on is a framework that I plan to use in an iPhone app of my own but which I am also trying to write for the "lowest-common-denominator" so that I (and others) can use it in other apps written for both Mac and iPhone.
Not only is this my first time writing an iPhone app, it is my first time writing for any Apple platform. In fact, it is my first time using Objective-C, period. I cannot stress this enough: I am a "n00b." So go easy on me. I also have not worked with threading before this, either, on any platform, so the learning curve for me here is rather significant, I'm afraid. I am NOT afraid of either taking the time to learn something properly OR of rolling up my shirtsleeves and working. However, on account of my experiences so far, I am finding myself (not to flame or anything!) quickly becoming frustrated by and disillusioned with not so much Objective-C itself, but the Foundation frameworks.
So with that said, read on, if you dare...
The basic idea behind my project is that the framework I am writing will present an API to developers which will allow them to write client apps that interact with a particular network appliance or network-aware embedded system. I already have my basic set of classes up and functioning, and the framework works to my satisfaction both on MacOS and iPhoneOS. The platforms I am targeting are MacOS X Tiger 10.4 and later, and iPhoneOS, and up until this point, I've managed to keep a codebase that works on all of the above.
What I wanted to do next was add some multithreaded goodness to the mix. (Woe is me.) I have asynchronous network socket I/O working within the main thread, and it, in fact, works a treat. In my test app on the phone, I've managed to keep the UI nice and responsive by using the main thread's runloop efficiently. But even though TCP async I/O works fine within the main thread, I want to be able to split out and offload the processing of any data received by the app from the appliance to its own thread. (It is possible, and even desirable, for an application using this framework to be connected to multiple appliances simultaneously.)
My idea, in order to try to keep things as simple and as clean as possible, was to implement a wrapper class that presented my other main class as an "actor." So, rather than instantiating my main class, one would create an instance of the wrapper class which would in turn control a single instance of my main class and spawn its own thread that the network connection and all data processing for that particular connection would run within.
(I hope I'm making sense so far...)
Out of the gate, writing a subclass of NSThread sounds like the logical design choice for an "actor-type" thread, but because I was trying to maintain Tiger compatibility, I stuck with +detachNewThreadSelector:etc.
Once I decided to pursue the actor model, though, the main problem presented itself: how to best pass messages between the main thread and all of the "actor" threads that might be spawned?
I stumbled upon -performSelector:onThread:withObject:, and knew instantly that this was exactly what I was looking for. Unfortunately, it doesn't exist on Tiger; only its much more limited little brother -performSelectorOnMainThread:withObject: does. So I kept looking.
All of the pre-Leopard documentation, tutorials, and sample code that I read indicated that to pass messages between threads, I needed to basically pretend that the threads were separate processes and use the expensive Distributed Objects mechanism to get messages back and forth. Unfortunately, even if that WAS a desirable option, iPhoneOS does not have any support for DO! Grrr...
Finally, I thought I found the answer when I ran into a third-party solution: the InterThreadMessaging library from Toby Paterson (available @ http://homepage.mac.com/djv/FileSharing3.html). In this library, the author basically implemented his own version of -performSelector:onThread:withObject: called -performSelector:withObject:inThread:. Sounds close enough, right? And actually, it is pretty darn close. It's made to do exactly what it sounds like, and it does it in a platform-neutral way that works on pre-Leopard systems as well as iPhoneOS, using Mach ports instead of DO.
(...wellll, ALMOST. I discovered after I built a small test app around it that it actually isn't "iPhone-clean." The author used an NSMapTable struct and the NSMap*() functions, which don't exist in iPhoneOS, and he also implemented the handlePortMessage delegate method, but although iPhoneOS has NSPort, it DOESN'T have NSPortMessage. GAAARGH. So I took the time to replace the NSMapTable stuff with NSValue-wrapped objects inside of an NSMutableDictionary, and replaced the handlePortMessage method implementation with a handleMachMessage method, which took some doing because I had to figure out the structure of a Mach message, NO thanks to ANY of the available documentation...)
Once I started using it, though, I quickly discovered that this implementation wasn't up to snuff. My "actor" class and my main thread will be passing a ton of messages to each other constantly whenever there is network activity, and with InterThreadMessaging, I found that whenever activity started to ramp up, it would collapse on itself. This mostly took the form of deadlocks. I found a note that someone else wrote after experiencing something similar with this library (quoted from DustinVoss @ http://www.cocoadev.com/index.pl?InterThreadMessaging):
"It is possible to deadlock this library if thread A posts a notification on thread B, and the notification on B causes a selector or notification to be posted on thread A. Possibly under other circumstances. I have resolved this in my own code by creating an inter-thread communication lock. When a thread wants to communicate, it tries the lock to see if another thread is already using the InterThreadMessaging library, and if it can't get the lock, it posts a message to its own run-loop to try again later. This is not a good solution, but it seems to work well enough."
So I tried implementing what he described using a global NSLock, and it did help with some of the deadlocks. But not all. I believe the culprit here is the Mach ports system itself (from the NSPortMessage documentation for -sendBeforeDate:):
"If the message cannot be sent immediately, the sending thread blocks until either the message is sent or aDate is reached. Sent messages are queued to minimize blocking, but failure can occur if multiple messages are sent to a port faster than the portís owner can receive them, causing the queue to fill up."
InterThreadMessaging in fact calls -sendBeforeDate: and exposes the deadline option, so I tried setting a really short time-to-live on the Mach messages and then intercepted any NSPortTimeoutExceptions that were thrown; upon catching said exceptions, I would then re-queue up the message to be sent again. It worked, but Performance. Was. A. Dog. At least the message queue wouldn't be full indefinitely anymore, causing the main thread to block, but during the whole time that these messages were expiring because the queue was full and then being re-queued, either the main thread was trying to send more messages or the actor thread was trying to send more messages. And as far as I can tell, the Mach ports queue is global (at the very least, there is seemingly only one per process). The message would get through with this model...eventually.
JUST IN CASE the problem happened to be something I screwed up as I was rewriting portions of the InterThreadMessaging library so that it would compile and work on the iPhone SDK, I substituted in the original version of the library in my Mac test app to see if any of these problems became non-issues. I found that both versions of the library -- mine and the original -- performed identically. So that wasn't it.
Finally, in frustration I said, "screw it, I'm going to try it the Leopard way," and replaced all of the method calls I was making to InterThreadMessaging's -performSelector:withObject:inThread: with calls to Foundation's native -performSelector:onThread:withObject: instead, changing nothing else within my code in the process. And wouldn't you know: IT WORKED GREAT. Performance was (and is) fantastic, about on-par with the non-threaded version when only dealing with a single connection/instance of my class.
So, in the end, I was able to do nothing to salvage the InterThreadMessaging implementation of cross-thread method calling, and as far as I can tell, I'm out of (good) options. And thus my mind is filled with questions:
How is the Leopard -performSelector:onThread: method implemented? I'm guessing not using Mach ports, given that I didn't have the same blocking & deadlocking problems I had with InterThreadMessaging. Is it possible to re-implement this Leopard+ method in a similar manner as a category to NSObject under Tiger? Or is it possible, perhaps, to increase the size of the Mach ports queue so that InterThreadMessaging works at a sane level of performance? Or -- I'm getting desperate here -- is there any way that I could trick -performSelectorOnMainThread: to target a different thread instead? (I am assuming here that -performSelectorOnMainThread is implemented under-the-hood much like the new -performSelector:onThread: is implemented, but with a hard-coded NSThread pointer built-in to the code, and that the new method just exposes a more flexible interface to what is basically the same code. I'm probably wrong...) Is there another third-party library out there that I've missed that fits my requirements for being able to do message-passing between threads in an efficient and portable manner?
I refuse to believe that there is no way for me to maintain compatibility with all of the platforms I wish to support without having to resort to making preprocessor #ifdef spaghetti out of my code. And there SURELY has to be a better way of doing cross-thread message passing in Tiger without using Distributed Objects, for Pete's sake! Is this really how people did it for years-on-end since the dawn of NeXT up until the advent of Leopard? And if there really, genuinely wasn't another alternative, then what is up with the lack of DO in iPhoneOS?? Does Apple seriously intend for developers who have good, solid, tested and working code to just chuck it all and start over? What if there was some aspect of DO that previous implementations relied upon that cannot be recreated with simple -performSelector:onThread: calls? (I don't know what those aspects would be...just a hypothetical.) I mean, I can understand needing to write new stuff from scratch for your UI given how radically different the interface is between the Mac and iPhone, but having to reimplement back-end guts such as something as elemental as threads...really?!
I do laud the inclusion of the new method in Leopard as well as the new ability to subclass NSThread itself. But for those of us that need to support Tiger for one reason or another, some of these restrictions and omissions within iPhoneOS seem like rather pointless (and frustrating) roadblocks.
As I hope is obvious here, I have tried to do my homework before throwing up my hands and pestering y'all. If you have the patience to deal with me, please tell me what I am missing.
Thanks for taking the time to read,
-- Nathan

Thanks again for your patience. Comments below.
etresoft wrote:
It is pretty unusual that anyone would want to call perfomrSelector on any thread other than the main thread.
What I described in my original post was not a worker thread, but an "actor."
It is hard for me to answer this question because there are so many options available to do "message passing". The fact that you think there are so few tells me that you really aren't sure what you need to use.
I didn't say there were few options for message passing. I said there were few options for message passing that fit my criteria, which are that any potential solutions should both A) work efficiently and with good performance, and B) be available both pre-Leopard AND on the iPhone. -performSelector: ain't available before Leopard. Distributed Objects is overkill. Kernel Mach messages apparently have a high overhead, too, as my experience with the third-party library I wrote about in my original message shows.
...consider notifications.
I thought notifications couldn't be posted across threads, either. How do I post a notification to another thread's default notification center or notification queue from a different thread?
The notification center is owned by the process. Each run loop can listen for just the notifications it wants. You don't "pass" or "send" notifications, you run then up the flagpole for all to see.
I am aware of how to use notifications. The documentation for NSNotificationCenter clearly states that "In a multithreaded application, notifications are always delivered in the thread in which the notification was posted, which may not be the same thread in which an observer registered itself."
So, again, I don't see how one thread can post a notification in such a way that the observer's registered method is executed in another thread (posting notifications "across threads"). This probably isn't a big deal if you are using mutexes (assuming you don't actually care which thread carries out the task associated with the notification posting), but as I said before, this is not what I'm after.
I don't know what you are really after.
Allow me to attempt to explain a second time, in a more concise fashion.
My app will have multiple, persistent TCP connections open, one connection per remote device. The user will be able to select a task to execute on a particular device that we have a connection open to, and get back from the application real-time updates as to the progress or results of the execution of that task. In certain cases, the length of the task is infinite; it will keep executing forever and sending back results to my application which will update its display of the results every second that ticks by until the user STOPS that particular task.
This can be done simply using async I/O in the main runloop, sure. But if I were going to thread this so that I could be processing the results I've received back from one *or more* remote devices while also doing something else, given that I will only have one (persistent) connection open to any given remote device that I'm interacting with (that is to say, I won't be opening up a separate TCP session for every single task I want to execute on a single device simultaneously), it makes sense _to me_ to implement this as I've described: with every connection to each remote device getting its own thread that lasts for the lifetime of the TCP session (which could be the entire time the application is running, times however many devices the user wishes to be connected to while in the app). I won't be spawning a new thread for every task the user wishes to ask a remote device to do.
This is why (I think) I need bi-directional messaging between the main thread and each of these threads dedicated to a given remote device that we have an active session with/connection to. The main thread needs to be able to tell remote device X (which already has a running thread dedicated to it) to do task A, and then get real-time feedback from that remote device so that the main thread can be displaying it to the user as it is coming back. Same with remote device Y running task B, simultaneously. At any time during the execution of these tasks, the user needs to be able to tell my app to stop one of these tasks, and the main thread needs to send that message to one of the remote devices via that device's dedicated thread.
This is why I am talking about this in terms of the "actor model," and not the "worker thread model," because the former model seems to fit what I want to do.
-- Nathan

Thunderbird is telling me that there is an unread message and it is one I read several days ago, listed in bold type again.

Every day or so Thunderbird says there is an unread message. I look for it and find it on the list of my messages received. It is in bold type as if it is unread. However I had read the message days ago.
I had this problem a couple weeks ago and decided to delete all the messages in my inbox. That solved the problem for a couple weeks, now it is back. I thought at first it was because my inbox was getting overloaded but now there are only a couple hundred messages in it. Maybe I should just uninstall Thunderbird and then install it again.

remove all mails from the inbox (Copy them to another folder or delete them. It makes litle difference.
Now Select File menu (alt+F) > compact folders.
I am guessing there is some corruption hiding away in there. A compact should fix it, but will do it better on an empty folder.

Why can't I use links within my email messages? When a link is clicked, nothing happens--it doesn't go to that specific website.

Why can't I use links within my email messages? When a link is clicked, nothing happens--it doesn't go to that specific website.

HI Ana ...
I had FB working again two days ago, and yesterday in mid-serve Safari just "couldn't find the server" once more...
That's a different issue...
First, if you can just use English, open System Preferences > Language & Text then select the Language tab. Drag English to the top of the list then restart your Mac.
Now for the server issue. Try using Open DNS. That shold help the "couldn't find the server" issue...
Open System Preferences / Preferences then select the Network tab. Click the Advanced tab then click the DNS tab.
Click +
Enter these numbers exactly as you see them here.
208.67.222.222
Click +
208.67.220.220
Then click OK.
Try accessing Facebook on Safari now.

Link to first unread message in a thread?

Similar Messages

Maybe you are looking for