I have a usercontrol and within it I declared a property P, when I use this userControl in a Page and I try to set P I have this error: is not recognized or is not accessible.
how can I solve this problem, thx
Related
String printMessage = driver.findElement(By.xpath("//*[#style='font-size:11.5pt']")).getText();
System.out.println(printMessage);
console error is:
Exception in thread "main" org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//*[#style='font-size:11.5pt']"}
as per the screen shot that you shared it seems that the element is within an iframe, You should switch to the iframe to interact with the element.
refer to the below link for more details
How to handle iframes
Why does my element throw the following error when it's served through an iron-component-page element (in a Polymer Seed Element demo), but not when served normally through my app?
Uncaught TypeError: this.hoodie.account.signUp is not a function
The demo is published at http://timblack1.github.io/hoodie-accountbar/components/hoodie-accountbar/.
this.hoodie should be created by hoodie.js, which does load according to Dev Tools' Network tab. But the this.hoodie object doesn't contain as many methods and attributes as it should, including the .account.signUp() method. this.hoodie.account exists, but only as an empty object.
I'm loading hoodie.js via a <script> tag in the hoodie-service element, which is loaded by hoodie-accountbar. Does the iron-component-page element do anything funny when it loads tags in a demo element? Or does hydrolysis?
#scarygami's comment pointed the way to the fix. The problem is that published properties are run through JSON.stringify(), which strips out any methods defined on those published property objects. So I fixed this error by no longer making the hoodie property be a published property on the hoodie-accountbar element. The fix is at https://github.com/timblack1/hoodie-accountbar/commit/db8d3071e4ad53a71b3d0e834075f00967c2e4a4.
I am trying to use the alternative page. I have the same problem with WinRTXamlToolkit.Controls.AlternativePage.
I add a AppShell : UserControl to my project but i can't navigate to the page. What else i must do?
You don't need AppShell to use AlternativePage. You need the AlternativeFrame.
I've embedded an image in my Flex mxml file (script section) using:
<fx:Script>
<![CDATA[
import com.views.myTitleWindowFile;
...
[Embed(source="com/assets/image_error.png")]
public static const IMG_ERROR:Class;
...
and it works fine. Now I want to use the same image in an mxml file named myTitleWindowFile (for a spark TitleWindow component), which was imported as shown above. The myTitleWindowFile.mxml gives an error on this line:
Alert.show("Please enter a value.", "Error",Alert.OK,null,null,IMG_ERROR);
The error states: 1120: Access of undefined property IMG_ERROR. Any idea what I'm doing wrong? Thanks in advance for any comments.
Your myTitleWindowFile shouldn't be accessing any resource in its parent. It can easily lead to a situation where you want to reuse that myTitleWindowFile in another area of your application that doesn't have IMG_ERROR defined.
I would just declare IMG_ERROR in myTitleWindowFile and access it locally. It keeps your code cleaner and more portable.
Im having problems with classpaths. I have used them before with "import" but I'm not able to link a class directly to symbol in the library.
I have a class c:/myfolder/src/myclass.as . In prefernces > AS3 settings, I have c:/myfolder/ as default classpath. I click linkage on the symbol and enter src.myclass . When I click the checkmark, it says 'class not found'. I am able to do: *import src.myclass; and attach the class to an instance on th stage. That works fine, but thats not what I need to do.
It's weird to use src as a package. Typically you'd set your preferences to c:/myfolder/src then put your top level package in there, but...
Check and make sure your file MyClass looks like this:
package src {
public class MyClass {
...
}
}
If it doesn't then you need to make sure your package matches the directories under your source directory (c:/myfolders).
Also you probably need to include the fully qualified package on the embed tag.
I found the answer. In preferences > AS3 settings the folder "c:\myfolder\" was below ".\". Once I moved it above, it saw the definition normally.