Re: Problems with a standalone for Linux (SOLVED) accents again ; -((
Bonjour, My problem was : On Tue, Feb 9, 2010 at 3:08 AM, Andre.Bisseret andre.bisse...@inria.fr wrote: Bonjour, I have an app. that I saved as standalones for the three platforms (Mac, Windows and Linux). A first stack is launched which includes the engine and 3 buttons, each of which opens an independant stack (say stack1, stack2 and stack3). The 3 buttons have exactly the same script (on mouseUp, they call a same command ouvrirCeStack). They are working well on Mac and Windows ; But one user of Linux reports that only the two first buttons are working normally. The third one does not open the corresponding stack!!! How is that possible ?? Quite simply ;-), it was because the name of stack3 included an accented character (Études) As soon as I renamed it as Etudes the third button opened it normally! Another problem with this Linux standalone : On stack1 (which open normally) there is a button help which alternatively change the visibile of a field help (shows or hides it) Here again works well on Mac and Windows but, with the Linux standalone, my user says that when he clicks on this button the field help is shown but is immediately hidden, and the stack is closed!! Here again the name of the field included an accented character (Démarches) With Demarches the button opened (or closed) the field as expected. So, for Linux standalones, accents are disastrous, but seems that it is only if used in the scripts. Fortunately the accents can be kept visible on the interface, thanks to the label feature : name without accent, but label with the accent(s) Assuredly, it appears that Linux does not like French ;-)) Thanks again to Sarah and Bernard Devin for the attention they paid to this problem. Best regards from Grenoble André ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Problems with a standalone for Linux
On Mon, Feb 8, 2010 at 5:08 PM, Andre.Bisseret andre.bisse...@inria.fr wrote: But one user of Linux reports that only the two first buttons are working normally. The third one does not open the corresponding stack!!! How is that possible ?? Andre, This is maybe not what you want to hear. I build a message logging feature into my applications. Throughout my code I have messages sent to the log, along with a priority level and a message. This means that debugging can be done outside the IDE by seeing what is in the log. logMessage 3, going to open help stack logMessage 2, user selected exit That way by setting a variable at the start that turns logging on my app can produce a log of events. And by setting the priority level I can determine how verbose the logging is. I know it's of little help to you in this situation. Unless you re-write your application to do messsage logging. It is probably less effort to install Linux in a VM and then run your app within the IDE and see what's happening. Bernard ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Problems with a standalone for Linux
Thanks a lot Sahah for your attention and your answer Le 8 févr. 10 à 23:14, Sarah Reichelt a écrit : On Tue, Feb 9, 2010 at 3:08 AM, Andre.Bisseret andre.bisse...@inria.fr wrote: Bonjour, I have an app. that I saved as standalones for the three platforms (Mac, Windows and Linux). A first stack is launched which includes the engine and 3 buttons, each of which opens an independant stack (say stack1, stack2 and stack3). The 3 buttons have exactly the same script (on mouseUp, they call a same command ouvrirCeStack). They are working well on Mac and Windows ; But one user of Linux reports that only the two first buttons are working normally. The third one does not open the corresponding stack!!! How is that possible ?? Is stack3 correctly built into the standalone? It is not in the standalone. As the 2 other stacks it is called by its fileName Is the a preOpen.. or open... handler in stack 3 that could be causing an error? No there is no such handlers Can you build a version which displays the result if there is a problem - that would help work out what the error is? OK, I will search how one do that and try ;-) Another problem with this Linux standalone : On stack1 (which open normally) there is a button help which alternatively change the visibile of a field help (shows or hides it) Here again works well on Mac and Windows but, with the Linux standalone, my user says that when he clicks on this button the field help is shown but is immediately hidden, and the stack is closed!! Perhaps he is double-clicking on the button which would show then hide. That was my first hypothesis but he said he does not double-click One way to avoid this is to have the button show the help field, and then a click in the help field itself hides it. I have the two possibilities to hide the field (click on the field or re-click on the button Not easy for me to find what is wrong with the Linux version. I have no opportunity to make quick trials and my user lives in another town (I sent him the app on a CD). Anyway, thanks much again Sahah Best regards from Grenoble André ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Problems with a standalone for Linux
Thank you very much Bernard for your answer. I will keep in mind your clever idea of a message logging; well, but for future applications ;-)) What I don't understand at all is why all is working well on Mac an Windows and not on Linux ! all the more so that, with Linux, among 3 buttons triggering exactly the same program, only one does not work! For the time being, I think that your last suggestion (installing Linux in a VM) should be the good one; But up to now, I sent my app. to only one person who uses exclusively Linux (and I am not selling it ;-)) so I will wait and see. Procrastination is not often a good solution but might be one in this case ;-o))) Thanks again Best regards from Grenoble André Le 9 févr. 10 à 10:06, Bernard Devlin a écrit : On Mon, Feb 8, 2010 at 5:08 PM, Andre.Bisseret andre.bisse...@inria.fr wrote: But one user of Linux reports that only the two first buttons are working normally. The third one does not open the corresponding stack!!! How is that possible ?? Andre, This is maybe not what you want to hear. I build a message logging feature into my applications. Throughout my code I have messages sent to the log, along with a priority level and a message. This means that debugging can be done outside the IDE by seeing what is in the log. logMessage 3, going to open help stack logMessage 2, user selected exit That way by setting a variable at the start that turns logging on my app can produce a log of events. And by setting the priority level I can determine how verbose the logging is. I know it's of little help to you in this situation. Unless you re-write your application to do messsage logging. It is probably less effort to install Linux in a VM and then run your app within the IDE and see what's happening. Bernard ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Problems with a standalone for Linux
On Tue, Feb 9, 2010 at 3:08 AM, Andre.Bisseret andre.bisse...@inria.fr wrote: Bonjour, I have an app. that I saved as standalones for the three platforms (Mac, Windows and Linux). A first stack is launched which includes the engine and 3 buttons, each of which opens an independant stack (say stack1, stack2 and stack3). The 3 buttons have exactly the same script (on mouseUp, they call a same command ouvrirCeStack). They are working well on Mac and Windows ; But one user of Linux reports that only the two first buttons are working normally. The third one does not open the corresponding stack!!! How is that possible ?? Is stack3 correctly built into the standalone? Is the a preOpen.. or open... handler in stack 3 that could be causing an error? Can you build a version which displays the result if there is a problem - that would help work out what the error is? Another problem with this Linux standalone : On stack1 (which open normally) there is a button help which alternatively change the visibile of a field help (shows or hides it) Here again works well on Mac and Windows but, with the Linux standalone, my user says that when he clicks on this button the field help is shown but is immediately hidden, and the stack is closed!! Perhaps he is double-clicking on the button which would show then hide. One way to avoid this is to have the button show the help field, and then a click in the help field itself hides it. Cheers, Sarah ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
