I have been using the Mac & Win client and I have found the Mac version to be a bit flaky. The UI has a tendency to become slow and unresponsive. I also have noticed that when you close the roster window you can not reopen it by clicking on the icon in the Dock. You can get it to show up id you go into the Spark Prefs, but the roster will not function after that and you have to quit and relaunch the app. I have tested it on 10.2.x - 10.4.4 (10.4 worked better) with similar results. Is there anything that can be done or do I have to wait for an update?
Client forget the settings I have set, like use 5223 and server address, even when settings are stored in XML files.
New Account, Advanced, and Login button has a strange affect around them, one letter in each have are underline on them and not on others. Also a aqua style button appears when the mouse moves over them but the sizes are wrong and should not have a white square background.
I have also notice that the client has from time to time not open the login screen. The application is open but no login window, the only way to get Spark to open right is to delete the Spark folder that houses the setting XML files.
Is there a complete list of issues that are going to fixed in the next release? Just wanted to see what else there is. I,am just to lazy to look though all the posts :& .
I have had a problem with the Mac problem quitting and then not being able to sign back in, it just hangs at authentication. I didn’'t see anything like this in the bug list…did I miss it?
Thanks for the feedback Grant. I’‘m happy that the 1.1 build is working better for you We’'ve been making a real effort to make sure that the Mac and Linux builds are up to par with the Windows build.
As for your issues
Bookmark room issue - SPARK-217
Client forgets “Show Empty Groups” on relaunch - SPARK-216.
I have been testing the new 1,1,1 Spark client, NICE JOB on the fixes. The client works really well now and I can see that this client is on its way. There are still a few bugs but the major ones seem to have been fixed. It’'s nice to see people actually listen and fix known issues.
I just wanted to say thanks to the dev team and programmers. Keep up the great work.