I have a project that was last run earlier this year. I've installed latest netbean with plugin but get the following when I start the app.
java.io.UTFDataFormatException: malformed input around byte 200
at java.io.DataInputStream.readUTF(DataInputStream.java:656)
at java.io.DataInputStream.readUTF(DataInputStream.java:564)
at com.codename1.ui.util.Resources.loadTheme(Resources.java:1270)
at com.codename1.ui.util.Resources.openFileImpl(Resources.java:303)
at com.codename1.ui.util.Resources.openFile(Resources.java:269)
at com.codename1.ui.util.Resources.<init>(Resources.java:189)
at com.codename1.ui.util.Resources.open(Resources.java:768)
at com.codename1.ui.util.Resources.open(Resources.java:688)
at com.codename1.impl.javase.JavaSEPort$4.run(JavaSEPort.java:1720)
at com.codename1.ui.Display.processSerialCalls(Display.java:1056)
at com.codename1.ui.Display.mainEDTLoop(Display.java:873)
at com.codename1.ui.RunnableWrapper.run(RunnableWrapper.java:120)
at com.codename1.impl.CodenameOneThread.run(CodenameOneThread.java:176)
I did create a sample app that worked and noticed that the properties tab shows it as a Gui Builder Project. My older project does not show this. I have tried comparing the properties but I do not see what is determining this.
I also copied the theme and the sample code into my project, used that as the main class. The problem still persists.
Any help would be appreciated.
Thank you
Sam
We updated the format of the resource files so newer skin updates might collide with this project. If you use Update Client Libs it should work fine.
However, this change might also cause issues with newer skins if you are using versioned builds. Since the skin includes the native device theme within and we updated the theme file builtin the skin. You can understand our motivation for this change by looking at the before/after screenshots in our 3.8 release announcement.
As a workaround for that problem you can switch a skin and download an older version of a device skin from our skins project. You can then add that skin manually and use that.
Related
I am preparing a WPF app to be released, I have about 5 modules (Class Libraries) along with the main app (Windows Application), should I change all the modules and the application build configurations from Debug mode to Release mode? or is it enough to only change the Main App build configuration mode to Release?
Toolbar
You can refer to the toolbar and select specific configuration for the current solution. It will automatically change building configuration for the all projects included in the solution itself (in spite of any dependencies between projects).
In case if you cant see the configuration combobox in toolbar, try to add it using the Standard Toolbar Options button.
Configuration Manager
Used for detailed building configuration management. Change configuration and platform options here both for one single project or the whole solution.
Menu bar/Build/Configuration Manager
Security
Unfortunately or not, but there is no solution to ensure the complete security of the application. We can combine a bunch of different techniques, but thats still not secure enough.
Please refer to first, second answers of this question to get details.
Change all to Release with the main app as well and build. There is no reason to have debug code, for size and security, in released software.
We have a situation with word addins where we try to load our taskpane and use cefglue implementation to show web page. We use cefglue for the same. We just discovered that one of the vendor addins also loads chromium but an older version. Unfortunately our addin shows a message that it cant load chromium due to hash difference.
Now is it possible that 2 COM addins can load different version of chromium? The vendor change looks unlikely and I could see they don't use cefglue or cefsharp but have their own implementation. Has anyone in this situation before? We are thinking of moving our code base to use same version as theirs but again when they upgrade, we have to upgrade and we will have a window where this fails due to incompatible version. thanks
It seems there is no easy answer to this problem as word / excel can load only one libcef dll in memory. The redgate apphost could be a possible solution and I added a link to cefsharp remoting repo which I am still trying to make work but has some readymade code and could be a good starting point for someone trying to do the same thing. Best of luck and thanks #amaitland for pointers.
Strange issue I'm having and I want to know what to do to fix it without compromising project integrity.
I have a CN1 project in Intellij (v 2017.1.4) that I started a long time ago. The other day I started a new CN1 project to try out something new. It pulled down the latest CN1 libs (the properties file says version 174 is the libVersion) and worked fine for testing.
Now I open my original project and the CodenameOne functions are all greyed out (projectLibs version in the properties file is 159). The icon on the context menu and menu-bar are greyed out. The plugin is up to date (3.7.2). I see no messages or errors in the IntelliJ "messages" section.
I am assuming that the new project and libs re-wrote something common to both projects and now the old project can't even start the plugin to let it pull down new libs... In experimenting, I went to my home directory ~/.cn1Settings and renamed the "CN1Preferences" file so that the project would have to create a new one. When I opened the project it DID create a new one and the plugin was working.
So here's the big question: If I abandon my old CN1Preferences file, what settings/customizations in that file am I walking away from and will I need to make sure I set correctly again to ensure my project works as it should and doesn't have any hard to debug issues?
This is probably an issue of keeping two windows concurrently, try closing both projects and opening only one at a time. There is an issue with detecting the correct project in the IntelliJ/IDEA plugin
I am working on an mvvmcross solution. I am making a wpf project as well to speed up the core development. Today I ran into an issue running a wpf project using a core that has the network plugin. When the setup.Initialize() is called I end up with the exception "Could not load file or assembly 'Cirrious.MvvmCross.Plugins.Network.Wpf' or one of its dependencies. The system cannot find the file specified.". I did include the network plugin from NuGet to my wpf project as well. Anyone know what might be the issue here?
Thank you!
i only added the wpf version of that plugin 5 days ago - https://github.com/slodge/MvvmCross/commits/TibetBinding/Plugins/Cirrious/Network/Cirrious.MvvmCross.Plugins.Network.Wpf
It hasn't yet made it to nuget - when it will depends on my work schedule and my hotel wifi - 'soon' is all I can say.
You can build it for yourself if you need it urgently - on the tibetbinding branch (see link above)
I've been looking around to find the release notes for the latest releases but I couldn't find it. Anyone have a link?
Different parts of the project have different logs of the changes between versions. The most comprehensive changelog for the project is the one for the Java language bindings, and it can be found here. Other portions of the project may have their own changelogs, but they are usually limited to changes only within that part of the project. Examples include the changelogs for the .NET language bindings and for the IE driver standalone server.