When entering a code line in Aptana Studio like
<input id="send" type="button" value="Send" onclick="calculate()" />
Aptana shows a warning: "input proprietary attribute onclick".
I wonder if this is a bug. There was a similar problem just a few days ago:
https://jira.appcelerator.org/browse/APSTUD-4873 called
"'button proprietary attribute onclick' is invalid warning"
Version: Aptana Studio 3, build: 3.1.3.201205292243
Yes, it is covered in that JIRA ticket and resolved in the latest nightly build of Aptana Studio 3.2.
Related
I checked a couple of tutorials and then dove in to Refactor>Migrate to AndroidX. I imported ActivityCompat, ContextCompat and DrawableCompat.
But now I am stuck getting a compile completed because of this error:
AAPT: C:\Program Data\Android\QiewProjects\DBQiew\app\build\intermediates\incremental\mergeDebugResources\merged.dir\values-v31\values-v31.xml:3: error: resource android:color/system_neutral1_1000 not found.
C:\Program Data\Android\QiewProjects\DBQiew\app\build\intermediates\incremental\mergeDebugResources\merged.dir\values-v31\values-v31.xml:4: error: resource android:color/system_neutral1_900 not found.
C:\Program Data\Android\QiewProjects\DBQiew\app\build\intermediates\incremental\mergeDebugResources\merged.dir\values-v31\values-v31.xml:5: error: resource android:color/system_neutral1_0 not found.
.
.
.
It continues on for about 21 missing items. It appears AndroidX is looking for color files that are missing.
I have spent hours looking for a similar posting, but there aren't any. I have even tried Invalidate caches/Restart but that changed nothing.
Please point me to an explanation to find the missing files or disable the hunt for them. BTW I am using Studio 4.1.2 and compile and target SDK versions 29.
It turned out I had to revise the compile and targetSDK versions from 29 to 31.
It was not mandatory, but I also upgraded the following versions in app/build.gradle:
androidx.appcompat.appcompat:1.0.0 -> 1.4.1
androidx.core.core:1.0.0 -> 1.7.0
androidx.constraintlayout.constraintlayout:1.1.2 -> 2.1.3
I would like to connect my arduino with modelica by using the firmataprotokoll and the arduinolibrary.
But the compilation always fails because of the error:
LINK : fatal error LNK1181: cannot open input file 'ModelicaFirmata.lib'
Does anybody have an idea how to fix this problem?
The error was caused by a wrong version of the Modelica-Arduino-Library. Instead of downloading the code I should have downloaded the latest release on github.
In addition it is important to choose the right compiler in Modelica (Visual Studio 2015).
I upgraded to Xamarin.Forms 3.6 and the following error occurs.
System.MissingMethodException: 'Method 'CanvasImageSource.get_SizeInPixels()' from assembly 'Microsoft.Graphics.Canvas' was not included in compilation, but was referenced in ImageRenderer.GetDesiredSize(double, double). There may have been a missing assembly, or a dependency on a more recent Windows SDK release.'
The error occurs on this line:
Absoluate.Layout.SetLayoutBounds(navigationlayout, new Rectangle(0, 0, 1, 46);
In Xaml, navigation layout is
<StackLayout x:Name="navigationlayout" Orientation="Horizontal" AbsoluteLayout.LayoutFlags="WidthProportional">
...
</StackLayout>
I also installed the latest pre-release Xamarin.Forms 4.0.0-pre5 gives the same error.
Reverting back to Xamarin.Forms 3.5.0.169047, the app runs normally.
I found the answer in Github.
(1) In UWP project, install Win2D Nuget package.
(2) In UWP project, set the minimum target to Windows 10, version 1803 (10.0; Build 17134)
Update to Xamarin.Forms 3.6. Viola, the UWP app runs smoothly.
I am trying to upload an assembly in Tridion Content Manager through the following post build event of a project in Visual Studio:
C:\Users\\Documents\Visual Studio 2010\Projects\\\bin\Debug\name of dll
Config.xml has been created through cmd as follows:
<?xml version="1.0"?>
<templateAssemblyUploadConfig>
<targetURL>http://<url>/</targetURL>
<userName>domain\user id</username>
<password>password</password>
<uploadPDB>false</uploadPDB>
</templateAssemblyUploadConfig>
When I try to build the DLL , it is giving the following error.
Error 1: Unexpected argument: Unexpected argument Studio C:\Users\\Documents\Visual Studio 2010\Projects\\\bin\Debug\name of dll\EXEC name of DLL
Error 2: The command " C:\Users\\Documents\Visual Studio 2010\Projects\\\bin\Debug\name of dll" exited with code 1. name of DLL
Can someone help in solving the issue.
Make sure that you use 'Space' and not the 'Enter' button in between the command.
Great to see the help by Huston.
you may also try a visual Studio Add-In which allows to upload dll(s) into Tridion in a more easy way
http://sdltridionworld.com/community/2011_extensions/AssemblyUploader2.aspx
This is my post-build event:
E:\Tridion\bin\client\TcmUploadAssembly.exe e:\Tridion\bin\client\config.xml "$(TargetPath)" /folder:tcm:43-61362-2
After upgrade XCode from 4.2 to 4.3 I've got below problem. I can't build it.
Do you guys have idea how can I resolve this problem? even some clue would be helpful to me.
ld: warning: ignoring file /Applications/Xcode.app/Contents/Developer/Library/Frameworks/SenTestingKit.framework/SenTestingKit, missing required architecture armv7 in file
Undefined symbols for architecture armv7:
"_STComposeString", referenced from:
-[NSMutableURLRequest_ParametersTest verifyDefaultParametersForRequest:] in NSMutableURLRequest+ParametersTest.o
-[NSMutableURLRequest_ParametersTest verifyModifiedParametersForRequest:] in NSMutableURLRequest+ParametersTest.o
-[NSMutableURLRequest_ParametersTest verifyEmptyParametersForRequest:] in NSMutableURLRequest+ParametersTest.o
-[NSString_URLEncodingTest testURLEncodedString] in NSString+URLEncodingTest.o
-[NSURL_BaseTest testURLStringWithoutQuery] in NSURL+BaseTest.o
-[OAHMAC_SHA1SignatureProviderTest testSignClearText] in OAHMAC_SHA1SignatureProviderTest.o
-[OAMutableURLRequestTest testGenerateNonce] in OAMutableURLRequestTest.o
...
"_OBJC_CLASS_$_SenTestCase", referenced from:
_OBJC_CLASS_$_NSMutableURLRequest_ParametersTest in NSMutableURLRequest+ParametersTest.o
_OBJC_CLASS_$_NSString_URLEncodingTest in NSString+URLEncodingTest.o
_OBJC_CLASS_$_NSURL_BaseTest in NSURL+BaseTest.o
_OBJC_CLASS_$_OAHMAC_SHA1SignatureProviderTest in OAHMAC_SHA1SignatureProviderTest.o
_OBJC_CLASS_$_OAMutableURLRequestTest in OAMutableURLRequestTest.o
_OBJC_CLASS_$_OAPlaintextSignatureProviderTest in OAPlaintextSignatureProviderTest.o
_OBJC_CLASS_$_OARequestParameterTest in OARequestParameterTest.o
...
"_OBJC_METACLASS_$_SenTestCase", referenced from:
_OBJC_METACLASS_$_NSMutableURLRequest_ParametersTest in NSMutableURLRequest+ParametersTest.o
_OBJC_METACLASS_$_NSString_URLEncodingTest in NSString+URLEncodingTest.o
_OBJC_METACLASS_$_NSURL_BaseTest in NSURL+BaseTest.o
_OBJC_METACLASS_$_OAHMAC_SHA1SignatureProviderTest in OAHMAC_SHA1SignatureProviderTest.o
_OBJC_METACLASS_$_OAMutableURLRequestTest in OAMutableURLRequestTest.o
_OBJC_METACLASS_$_OAPlaintextSignatureProviderTest in OAPlaintextSignatureProviderTest.o
_OBJC_METACLASS_$_OARequestParameterTest in OARequestParameterTest.o
...
ld: symbol(s) not found for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)
I was getting the same linking error for the Simulator after upgrading from Xcode 4.2 -> 4.3.1. I noticed that new projects in 4.3.1 do work with Unit Tests, so just compared the project differences.
What fixed it for me was:-
Select Project in project navigator
Select Test Target
Select Build Settings
Go down to Framework Search Paths and single-click it
Delete whatever is there
Enter $(SDKROOT)/Developer/Library/Frameworks $(DEVELOPER_LIBRARY_DIR)/Frameworks
If you had any custom frameworks, add those back
Actually, Unit Tests run fine on the Device, too.
Looks like this was either an accidental (or on purpose) omission on Apple's part.
If (and only if) you are a registered Apple Developer, you can log into the Apple Developer Forums and if you copy this linked search query into your browser address bar, you will see other people have had the same problem.
For now, it looks like you can only use SenTestingKit on the simulator.
I had a similar issue with Xcode 4.4.
My solution path:
Removed SetTestingKit.framework from the main target's (the system under test) "link binary with libraries", leaving it in the test target as is. Not sure why it ended up there in the first place.
I believe this bug is now fixed in Xcode 4.4.1
Using xcode 4.6 and trying to add facebook SDK 3.1 I had this problem because I didn't select to add the files to my test target.
You should check both targets when you copy the framework.
I just upgraded to 4.3.1 There is a problem with SenTestingKit framework. I removed the test source code from the project, it builds ok. And it can run on 5.1 device. But I got _dyld_dyld_start error when I ran it on simulator. I had to remove SenTestingKit from the project to make it work on simulator.