I have found this article:
http://jomnius.blogspot.de/2011/06/how-to-find-unlocalized-strings.html
It describes how to specify NSShowNonLocalizedStrings in your app to make the console print out untranslated locale.
Where and how do I have to specify this option in MonoDevelop?
Related
I'm trying to pass the argument -FIRAnalyticsDebugEnabled to my Xamarin iOS App but I seem to not have found the correct place in Xamarin Studio to put it. I tried as additional mtouch argument like
--argument=--app-arg=-FIRAnalyticsDebugEnabled
or
--argument=-FIRAnalyticsDebugEnabled
but neither worked.
I keep seeing this line in the application output:
Firebase Analytics v.3402000 started
To enable debug logging set the following
application argument: -FIRAnalyticsDebugEnabled (see
goo.gl/Y0Yjwu)
The google short link doesn't link anywhere anymore
According to https://bugzilla.xamarin.com/show_bug.cgi?id=43899 the fix seems to be to add the following text to "Extra mlaunch Arguments":
--argument=-FIRAnalyticsDebugEnabled
The help for configure in Qt commercial source 4.8.7 lists an option "-commercial" with the following description.
-commercial ........ Compile and link the Commercial Edition of Qt.
The options are also listed here, with the same brief explanation of this parameter, http://doc.qt.io/qt-4.8/configure-options.html
Since there are separate source packages for commercial (or enterprise) and open source, why is a flag needed? Also I can confirm that it successfully compiles also without giving this flag, which makes me wonder even more...
What does it actually do?
If you configure without commercial or opensource option you get asked with which license you want to use Qt: the commercial or the opensource one. I assume using one of these options just pre-answers this question.
EDIT: Sorry, I mixed something up. Forget the "answer".
In want to suppress warning message generated while installing application through Installshield Environment.
Is there some kind of CONDITION that can be put in the Installshield Application builder while creating Installation file ?
There are two possibilities and I'm not sure which your scenario is. But just make sure you have turned off COM Extract at Build for the component (if you see the warning at build), and marked it not Self-Registering (if you see the warning during installation).
I think at least the latter is a right-click file property in Express editions instead of an option on the component grid (as there is no component grid in Express editions).
I'm trying to develop a portable J2ME appli, but Netbeans do a class preverification of LWUIT library that uses optional APIs that some configurations don't have, so I get this error when I try to compile on a configuration without JSR-184 (M3G Optional API):
Error preverifying class com.sun.lwuit.animations.Transition3D
VERIFIER ERROR com/sun/lwuit/animations/Transition3D.initTransition()V:
Cannot find class javax/microedition/m3g/Node
I don't want to remove the classes from the LWUIT API because that classes works on other configurations compatibles with JSR-184
What I want is that NetBeans do not preverify the library, It is posible?
Here are some code:
//#ifdef JSR184
//# import com.sun.lwuit.animations.Transition3D;
//#else
import com.sun.lwuit.animations.CommonTransitions;
//#endif
Transition out;
//#ifdef JSR184
//# out = Transition3D.createRotation(500, true);
//#else
out = CommonTransitions.createSlide(CommonTransitions.SLIDE_HORIZONTAL, true, 500);
//#endif
setTransitionOutAnimator(out);
Thanks
We had the similar problems, as I remember BlackBerry handsets are problematic (?) for this JSR-184. What I did to solve this problem, I created different configurations for different targets and removed this problematic classes from LWUIT library, rebuild library for that target, and also modified project settings of related configuration accordingly. Hope it helps.
There is a native blackberry port of LWUIT as well as quite a few tutorials and instructions on how to use it. The native port uses native RIM API's which work far better on the blackberry devices than MIDP API's.
LWUIT's use of 184/226 doesn't bother devices that don't support these profiles other than blackberry which has a broken classloader implementation.
It may be possible, though I havent tried it. Netbeans has two xml files, build.xml and build-impl.xml. Look at these files and look for preverify task, then you can do a bit of testing and ensure that it doesnt preverify the library.
Netbeans ant plugin is a pretty simple setup and you can change it which ever way you want to.
I'm trying to export a profile from WAS 6.1 so that I can give it to other members of my team with all of the JNDI and Shared Library configurations in place. I've flowed a few IBM tutorials on this like http://www-01.ibm.com/support/docview.wss?uid=swg21322309 (technically that is more a bug fix, but there is a similar page). I've tried to export the server using the "import" feature of the server in RAD 7. None of these options create a .car file with the resources sticking around.
Does anyone know how to do this?
Thanks,
JPD
Have you tried exporting/importing the WAS configuration using the wsadmin console as described in the following IBM TechNote?
https://www-304.ibm.com/support/docview.wss?uid=swg21207526
Unfortunately, the SIB configuration will be missing from the export -- I'm not sure if it's a bug or a feature, but it's at least mentioned by IBM in their TechNote so you don't have to pull out your hair searching for the problem.