Hmm. I'm not sure what's going on. I'll try to explain how this is supposed to work, but I'm not sure what to do about it.

The communication between the GUI and the Poser server changed from P8 to PP2010. In P8, the GUI was constantly polling the server to learn the state of the universe with regard to what ops are allowed at any given time. As you change rooms or change the content in the scene, or change the selected figure or actor, the GUI has to react in near real-time. So the P8 GUI was polling 4 times per second, via an HTTP request, to find out if the server had any important changes to any of these things that the GUI should be aware of. Mysteriously, quite a few users were reporting that these short but frequent conversations were being "recorded" in the browser cache, building up huge piles of temporary files. So for PP2010 we changed this. The GUI opens a permanent XML socket connection to the server. Over this connection, the server can "say" whatever it needs to say asynchronously. This has two benefits. One, the browser is no longer involved in the transaction, so any problems with it stupidly recording the conversation are gone. Second, neither the GUI nor the server are wasting CPU cycles saying "Any change?" and "No" over and over again. So background CPU usage drops to zero.

Now since this connection is internal, in theory it cannot "drop" spontaneously. So we made no provision for re-establishing the connection, since it is supposedly impossible for it go away without either party asking it to go away.

But - if it were to go away, then the GUI would no longer learn about state changes from the server, and as a result it would not present the + option when it should, i.e. after you add a figure. (Once a figure exists, there is always a "current figure", so the option should always be visible.)

So I'm saying that this may or may not be a cause for the disappearing + button.

However, you said that closing and re-opening the library doesn't fix it, and that disturbs me. If you completely close the AIR version of the library GUI, the XML socket connection is destroyed. Starting the GUI again should re-create it. Minimizing the GUI would not do this, but closing and opening it would. But since you said it didn't happen that way, it leads me to believe that this isn't a "lost connection" problem. Theory says it isn't possible, and your evidence indicates it isn't happening anyway.

So then we have to consider other possibilities. The only thing I can think of is there is an out-and-out bug in the server, where it isn't telling the GUI the truth. If I were sitting at your computer, I could figure this out pretty easily, but that isn't an option, so this is a stumper for me.

Has this been reported to SM?

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)