I had some application working in Awesomium 1.6.6 but then I upgraded to 1.7 because I needed to add a new functionality to old application which in old Awesomium version wasn't supported.
But now I run in deeper problems, all the API of Awesomium is different. I have changed much things and now my application works but here are the problems i experience.
I have a problem by changing headers: http://pastebin.com/HrgmAJZS in Awesomium 1.7
How i accomplish this in new version?
And I need to change JavaScript on off by clicking the button on a form. I have tried this http://pastebin.com/yU3StmWG but it doesn't seems to work.
Here is my full conversation on Awesomium discussion board: http://bit.ly/Zw3Ldi
Any help appreciated.
There is a known bug, that crashes a WebView or WebControl, when WebPreferences.Javascript has been set to false on the view's WebSession. This will be fixed in the final release of version 1.7.
Related
I am trying to use UWP(Community Toolkit) TabView Control, but it's throwing below exception:
Cannot find a Resource with the Name/Key UseSystemFocusVisuals [Line:
35 Position: 91]'
Min Version and Target Version both are set to Build 16299. As per this MSDN documentation, it supports device family Universal, 10.0.16299.0 or higher
Windows 10 OS build is 17763. If I change the target version to 17763 then it's working as expected.
Any reason why it's not working when the target version is set to 16299?
Strictly speaking this isn't the UWP control but rather Windows Community Toolkit control. As it isn't made by Windows team the documentation is based on the human input and clearly there can be errors in it. It may also be a bug, the best thing to do is to submit the issue to their github: https://github.com/windows-toolkit/WindowsCommunityToolkit/issues
With the input from #Ivan, I checked for similar issue on WindowsCommunityToolkit GitHub site and seems that this issue was already reported.
According to the discussion on the issue, Fix is already implemented but will only be available when a new version of the toolkit is published. So until then if anybody else wants to have a fix, you need to define UseSystemFocusVisuals in your App.xaml as below:
<x:Boolean x:Key="UseSystemFocusVisuals">True</x:Boolean>
While developing a Cocoa sandboxed application, I discovered that if I switched it to non sandboxed, in all the Open Panels of the application, the right click commands (Duplicate, move to trash etc.) do not work any more. I am certain they did work no more than two weeks ago, but I have reverted the project to old commits and the misbehaviour is still there. I tried everything, until I realised that this misbehaviour now appears in all my projects, if I switch them to non-sandboxed. This makes me think it may be some kind of bug introduced in 10.14.2 or something similar. I hope somebody else has experienced the same issue so that we can understand better what is going on. Thanks
P.S. I am using the latest Xcode 10.1 (10B61) and tried on several machines. It is the same misbehaviour.
The OS might be confused by having some contradicting leftover knowledge about sandboxed and non-sandboxed versions of the app with the same version / bundle ID / signature.
Some things to try:
Test the app on a fresh user account.
Delete the app sandbox container from your Home Folder > Library > Containers.
Temporarily change app bundle ID to something new to see if it’s still affected.
Apple's iOS 8 breaks certain tap functionality in versions of dojo prior to 1.9.4 (see Xpages mobile controls not working in iOS8
The current version of Dojo in Domino 9.0.1 FP2 is 1.9.2 but that does not fix the issue. You have to use at least 1.9.4.
I have downloaded 1.9.4 and placed it in the correct folder on our test server. But I cannot get things to work. I changed the folder name of dojo 1.9.4 to 1.4.0 as I only want to use this version for 2 dbs that are having the problem.
Question 1:
What line do I put in the xsp.properties file:
xsp.client.script.dojo.version = 1.4.0
xsp.client.script.dojo.path = / domjs / dojo-1.4.0
Question 2:
There are so many things to download when I go to the dojo download page. I downloaded the zip file and used that.
When I run code to test what version of dojo I have I get 1.9.4. But when I try to load my page, I get an error.
dojo._loaders: TypeError: dojo._loaders is undefined
Any help would be GREATLY appreciated.
You probably have the right dojo zip, this one: http://download.dojotoolkit.org/release-1.9.4/dojo-release-1.9.4.zip. As you say, unzip that to the dojo-1.9.4 folder in <server-install>\data\domino\js\, or name the folder 1.4.0 if you want to specify it for only a few apps.
You will indeed need to copy the IBM folder from the <server-install>\osgi\shared\eclipse\plugins\com.ibm.xsp.dojo_9.0.1.<date-stamp>\xsp.dojo.jar into your new 1.9.4 (or 1.4.0) dojo folder. Little chance of anything working without it. Copying the ibm folder from the 1.5.2 folder is a bad idea as that is old code, and you'd certainly have issues with it working with dojo 1.9.4. In Fix Pack 2, the ibm folder from the plugin was tested/designed to work with dojo 1.9.2 (the version in that jar), so it should play fairly nice with 1.9.4.
In your XPages app, in the xsp.properties, you should only need the line:
xsp.client.script.dojo.version = 1.9.4
Rebuild your app, restart the server etc, and you should be good to go.
DISCLAIMER: This is a work-around, not a supported solution by IBM. There may be unexpected issues using this approach. It's used at your own risk.
You commented already on that topic here so I think you tried this one? http://hasselba.ch/blog/?p=323
This is the SO thread: XPages mobile controls not working with iOS 8
I am working on an ArcGIS add-in (a very simple toolbar with a few buttons) with VB.Net and ArcObjects SDK in Visual Studio 2010. The solution was built successfully and the debug settings were configured.
When I hit Debug, ArcMap application was opened. I couldn't find the toolbar docked anywhere on the ArcMap toolbar. I went to "Customize" -> "Add-in Manager" and the add-in being debugged was not there. Then I tried "Add From File...", located the "esriaddin" file and clicked "Install Add-in". It populated a message box saying "No GUI components found in this Add-In."
I made some Google searches but haven't got any luck to reach a solution yet.
What was I missing? Has anyone come across the same issue and any direction?
Thanks in advance!
Try clicking build first, then open the arcmap separately and check the add-in manager inside of arcmap to see if it got added to the application. If so, you should be able to find it and turn the toolbar on.
I'm not sure about .Net, but I debugged this issue for the Java SDK. You have to make sure you are using the correct versions for compiling. In java, it was an old archive version of jdk1.6 32 bit.
Then I was referencing something wrong inside the xml document. I had changed the name of my JAR file (taken from project name by the ArcObjects SDK). In the xml document it was still pointing towards the old name.
This may not help you, but if anyone else searches this error and is using tje Java SDK, hopefully it will help.
I struggled with this same issue with a 10.0 add in. We had a 10.1 update that worked with 10.1 but trying to install it to 10.2.2 gave me that exact error. So much for upward compatible! I then tried to build 10.2.2 code and kept having this error. Others mentioned needing to build to x86 so I did that although the 10.1 was on Win7-64 and ran with AnyCPU....
I believe the final key for me was in the config file. I had set version to 10.2.2 As soon as I changed that to 10.2, the darn add-in installed just fine. Nice waste of a day for an extra '.2'
I have an OSX application written in Objective-C/Cocoa using xcode. The application is quite finished, tested and sold on the App Store.
I haven't worked on this application for some time and recently, I rebuilt it using xcode 4.3.3 on my OSX 10.7.4 and I noticed that while it builds just fine, there are some very strange visual glitches when running the application that were never seen before and occasionally, I get EXC_BAD_ACCESS when closing the application. All these seem to be related to the PDFKit framework I am using. I am unable to debug these problems since the glitches are just visual (nothing I can check in code) and EXC_BAD_ACCESS exception comes from internally allocated objects not related to my code.
The code itself haven't changed, I tried previous revisions of the code and they all exhibit the same strange behavior now. I tried running an old binary I have of the application (compiled couple of months ago) and it works just fine. Then I tried building it with previous versions of xcode, down to 4.2.1 (which I know was ok when I submitted the app to the app store) and the problems still occur.
Then I suspected this may be something specific to my environment so I built the project on different machine also with xcode 4.3.2 and OSX 10.7.4. Same results, the problems are still there.
So now I suspect that it has something to do with the OSX 10.7.4 update since this is the last thing that was changed between now and when I was able to produce a good build of the application. I am pretty puzzled to what to do next and how to identify the cause of this problem. I have an old binary that is working fine and I have a newly compiled binary of the same code revision that has problems.
Is there any useful information I can get from the difference of these binaries? What can I do to determine the cause of these problems? What can I try next?
Thanks!
NOTE (update): I stated it above but I want to make sure it is clear. This is a Mac OSX Cocoa application, not iOS.
just reset your simulator then try.
I hope you check the ARC information
go to your project Target set build settings --> Search Paths-->Always Search User Paths Set Yes.
And check your all class variables different from one another.
Xcode--> preferences-->Documentation check installed core Libraries (or) install it
like that
Xcode--> preferences-->Components check required component installed or not
check these things in your project.
Are you sure your customers are not having the same problem? Since you have tested the application on a different machine you probably do not have corrupt libraries installed (unless you did not install from scratch but used some migration tool?), so that is probably not the problem.
Most logical explanation to me would be that your customers also have this problem but they haven't reported it yet. In that case, you probably have a memory problem and there are techniques to attack that.
In any case, eliminate all the parameters that you can eliminate to simplify the problem. Deconstruct the application until the problem does not occur anymore or reconstruct the application in a different project until the problem occurs again.
It sounds like a nasty one, but you'll get there in the end, with patience and perseverance :)
First of all, you need check and verify the build log for suspicious compiler warnings.
For EXC_BAD_ACCESS, XCode analysis will give useful information.
You could try 10.6 or 10.5 (need manual installation) SDK. Or restrict the deployment target to 10.5 or 10.6.
I will answer my own question (since none of the above answers really answer it) so anyone with a similar problem might have a hint. I was not able to understand why exactly this happens but I'm pretty sure this is not a problem with my code but rather some glitch on Apple's side. And there is a workaround.
First, I compiled Apple's sample "PDF Annotation Editor" project on my Lion 10.7.4 and while the functionality is obviously different from my project, it also exhibited similar glitches with the PDFView display that my project does when compiled with 10.7.4
Then I proceeded to building a fresh clean system on new hard disk. Intalled Snow Leopard and upgraded to 10.6.8 and ONLY installed xcode. Compiled my project (the source code always stays exactly the same) and everything works fine. No problems seen in the compiled project.
Updated my OSX to Lion 10.7.4 and xcode 4.3.3, same source code. The problem is there after I compile it. I am pretty sure that if I tried 10.7.3 first, I would not see the problem as I remember it only starts with 10.7.4 but Apple doesn't provide any reasonable way to update to 10.7.3 first or downgrade to it after 10.7.4 is installed (shame on them, not very developer friendly!).
So, the problem appears in 10.7.4.
Then I installed the pre-release version of 10.7.5. This was the only thing that was changed, same source, same xcode. To my surprise, the compiled code works flawlessly now and the problems seen with 10.7.4 are now gone!
So my workaround - wait for 10.7.5 release before working on the project further. Hopefully Apple won't screw it in the future with Mountain Lion. I don't think I am going to try and debug it further or submit a ticket to Apple, going to be a tough case to explain.
Thanks for the responses.