We’re having a problem with Spark that we haven’t been able to resolve ourselves and thus though we would ask if anyone here knows what might be causing it.
As the title says, when we do broadcasts there is no indication on the recipients that they have recieved a message. They get the message so there is no issue there, although some cliens sometimes get blank messages but that’s a separate issue.
Can’t reproduce this with Spark 2.6.3. If i send a broadcast in Spark to other Spark users ( i select them in the Broadcast window), then they get a new message window and a popup about a new message (if popups are enabled), also the new message window is flashing. Tested on Windows XP/Win7 32 bit.
I can only confirm, that chat window is not flashing on 64 bit (i guess flashing dll has to be compiled for 64 bit), but i do get a new window when receiving a broadcast message. SPARK-1414
We only get a new tab in Spark, when receiving a broadcast message (as the previous version of Spark). But nothing indicates it =/
Is there a solution for the compilation in 64 bit of the flashing dll ? Maybe I can use the dll version of the previous Spark (strange manipulation but sometimes it’s possible) ?
we are preparing 2.6.4 or actually it is going to be 2.7.0 (since we move to Java 7). Can you provide a revised flashwindow.dll to be included in 2.7.0 beta?
There are tons of reports regarding w7x64 flashing issues (no compilation at hand right now for me). If you can assist us with flashing, I’ll review the w7x64 reports.
Sorry, been out of the loop for a while. Has there been any update to the source for the 32 bit version? All I did was re-compile the existing code into a 64bit dll. It should work exactally the same as the 32bit version. If the code has changed can you point me to the updated source?
I will check it out sometime next week. I don’t have visual studio at home.
I have re-compiled the dll using Java 7 for 64bit Windows.FlashWindow.dll
I installed this on my current Win7 64bit systems with the latest svn and did not have any problems with broadcasts or normal messages. Then again I wasn’t having any problems before either.
This issue is resolved for us now. What we did was go back to Spark 2.58 but this time we used the version with Java embedded and the broadcasts are back. Our other issues with Spark preventing the machine from shutting down, http://community.igniterealtime.org/thread/44970 , has also been resolved by using this version of Spark.
I can’t say if these issues are down to Spark, Java or our MSI packages of them but I’m just happy everything works now.
Not really no. The only thing I can think of would be some weird permission problem as our users are users on the machines as well but that feels weak. Other than that I’m afraid that I can’t offer anything more substantial than that Spark with baked in Java was our saviour.