I m automating a page where there is a popup and on that there is radio button and a submit button, when i click on radio button my test fail giving error that hidden object cannot be performed action like click but its visible (not hidden) where as when i click on submit button on same popup is click. i have checked its properties but there is nothing which i can change it just have simple id,name,value which is changing dynamicly and for that i have even used regex
please help me out
Thanks
It's possible that there is another radio button on the page with similar properties. Is this a recorded object? Is the popup window listed as the parent?
Can you post the Regex you are using, the control's properties, and the properties of the popup window?
if your are using IE whose version is > 9.0.19 then there was a patch release by Microsoft to overcome this issue
http://blogs.msdn.com/b/visualstudioalm/archive/2013/09/17/coded-ui-mtm-issues-on-internet-explorer-with-kb2870699.aspx
Related
I am new to Xamarin and want to develop an Xamarin.Form Portable App.For that, I have created the project template as Xamarin.Form Portable.
After login, I have successfully created a Master Detail Page to display the Menu List like Home, AboutUs, ContactUs links in the left corner which is initially hide and when i click on the Menu Icon (Menu Icon is like three dashes(-) in parallel) all Menu List is populated to the right side in window. Now when i click on any Menu Item,I don't want to repeat the menu list or its icon in the inner pages. Instead of that, I want Navigation back arrow button instead of the Menu Icon. When I tried to navigate it like below it gives me error like "PushAsync is not supported globally on iOS/Android, please use a NavigationPage"
await Navigation.PushAsync(new AboutUs());
If instead of this, I navigate it to the master detail page and set the About Us page as Detail property of the Master Detail Page then Menu Icon and Menu list will be reapeated which i don't want. Please help me how can i show the navigate the page with Back Arrow button in inner pages.
Overall, I want functionality like in Gmail where when we open any Detail of Email Menu button is not there but the back arrow button is there.
Thanks in advance!
Try this approach(Because DetailPage must be NavigationPage in Xamarin.Forms):
await Navigation.PushAsync(new NavigationPage(new AboutUs()));
When I cilck on a button on main toolbar, I am displaying a popup form (PXSmartPanel) with few fields on it. Whenever I click on the main toolbar button, I want first the control should go to the popup form and based on buttons on popup form (Ok/Cancel), it should perform the action.
However, I tried that but eventually when I click on button on main toolbar, it first executes the code behind for that button and then shows popup.
Any suggestions?
Found the solution. You can use AskExt method of your DAC class to show popup first and then execute your code.
You can also use px:PXSmartPanel with AskExt. With help of PXSmartPanel you can customize your screen, and even add some buttons to your pop up. Here I wrote "short" manual how to do it.
I've been doing searches trying to find help on this, but so far all I have found is how to set options for popping up a SharePoint modal dialog box from custom code.
However, I haven't created any custom web parts to display modal dialogs. What's happening, is if someone clicks the upload document button in a library, the upload document modal dialog comes up, but the ok and cancel buttons are half off of the bottom of the box. Users can click on them, but it just doesn't look very good.
I started playing with the CSS to make the modal dialog box bigger to reveal the buttons, and that works for the most part, but the real problem is the grant user permission dialog box.
When that is clicked, it doesn't show the ok and cancel buttons, and maximizing the dialog box doesn't reveal them. The user has to hit tab about 5-10 times before the focus moves to the ok button and is then clickable.
I would post an image, but I don't have enough reputation to do so.
Has anyone come across this? It seems very strange that the out of the box setting would have this problem.
The CSS that I use to adjust the height and width of the modal dialog is:
.ms-dlgFrame, .ms-dlgContent, .ms-dlgBorder, .ms-dlgFrameContainer
I'm just trying to set the height/min-height values, but I haven't had much luck.
We're using Internet Explorer 11 to view the pages.
Stevangelista actually pointed me in the right direction, I wish I could mark comments as answers, and since I'm new I can't upvote the comment, but here's the solution:
I am using a customized master page, and that comment had me take a look at the elements in the page.
Since the master page is being used in the dialog boxes as well, I used the s4-notdlg class to remove parts that weren't needed in the dialogs. Those parts were pushing the buttons below the bottom of the screen.
I'm not a css expert, so there may be ways of keeping those parts and still have the buttons accessible, but the particular issue I was trying to fix was resolved by using the s4-notdlg class to objects in my custom master page.
I'm trying to understand InstallShield (2009)/InstallScript on the fly, because I'm modifying someone else's installation script.
One of the dialogs during the installation procedure previously had one textbox on it, asking for a SQL Server instance, assuming a certain database name. Now I've just completed an enhancement enabling you to choose any database name, not just the default, and I need to add a field to this dialog so the user can input the chosen DB name. Monkey see, monkey do, just make a new control and duplicate and adapt whatever functionality the form had for the first textbox - easy enough, right?
Umm... problem here. It seems that the "SdShowDlgEdit1" form is a generic thing that gets shipped with InstallShield, and is used all over, wherever you have a dialog that needs one textbox. Change that form, and it changes everywhere that it's called... so now I have a spurious 2nd textbox appearing all over my installation wherever there was a single text box before.
Oops. Undo changes, and change the reference to "SdShowDlgEdit2", which is - you guessed it - InstallShield's standard form for dialogs needing 2 textboxes. Now that would be great.... excepting that the previous developer got there before me and added a "browse" button to that form for a place where he needed the 2nd text box to contain a folder path. I don't want that "browse" button, and I can't delete it.
So I think, why don't I create a custom form of my own, and not get under anyone else's toes? So I clone the form, rename the new instance to "EnterDbDetails", delete the "Browse" button and make the form look just right.
Then I go back into the InstallScript to redirect to "EnterDbDetails" and discover that the EzDefineDialog function requires me to pass in the "Resource ID" of the form. Now what was it again... 12018... great... fill in all necessary details, compile, build, and give it a whirl. Looks lovely, all the right default values are filled into the two text boxes - but hey! Why is the browse button there? And why is the text on the labels not what I set?
Back to InstallScript, check the Resource ID - turns out that the original "SdShowDlgEdit2" also has a Resource ID of 12018. Well, that explains that nicely. Silly that InstallShield allows you to have two forms with the same ID, but whatever... So let's go back to my "EnterDbDetails" form and change the ID...
... but the Resource Identifier property is read-only! WTF?
So now I can't use any of the standard forms, and I can't use a custom form because it won't let me change the resource ID.
I am stumped. Can anyone please explain how you are supposed to do something like this, which really ought to be the simplest thing in the world?
Creating New Custom Dialogs in InstallScript and InstallScript MSI Projects
Quote from the site (2015 edition) :
To create a custom dialog, you need to perform the following general steps:
Use the New Dialog Wizard to add a new custom dialog to your project. For more information, see Using the New Dialog Wizard to Add a New Custom Dialog to an InstallScript or InstallScript MSI Project.
Add controls to the dialog. For more information, see Adding a Control to a Dialog in an InstallScript or InstallScript MSI Project.
Create a script function that loads the dialog into memory, displays it on the screen, handles the end user’s interaction with the dialog’s controls, and closes the dialog when the user is finished with it. For more information, see Using InstallScript to Implement Custom Dialogs.
To create a new dialog:
Open the Dialogs view. The Dialogs view is located in the User Interface section of the View List.
Right-click the All Dialogs explorer and then click New Dialog. The Dialog Wizard opens. Click Next to dismiss the Welcome panel.
In the Dialog Template panel, click Interior Wizard Panel, and select the Let me insert this dialog in a User Interface sequence check box.
In the User Interface panel, select Installation in the User Interface Sequence list. In the list of dialogs, select InstallWelcome. Based on these selections, InstallShield will insert your new dialog in sequence immediately following the InstallWelcome dialog.
In the Dialog Position and Condition panel, leave the default settings, and click Finish. Your new dialog appears in the Dialogs list.
Right-click the dialog and select Rename. Rename the dialog WelcomeBitmap.
Using the same technique, you can insert additional dialogs in your installation’s user interface.
In this step, you will modify the WelcomeBitmap dialog that you just created:
First, create a bitmap (using a program like Microsoft Paint) that measures 300 by 150.
Open the Dialogs view.
Expand the WelcomeBitmap dialog’s node. Click English (United States) to open the Dialog Editor.
Click the Dialog Bold Title text box at the top of the dialog. In the Text field, type Welcome Bitmap. This changes the dialog’s main title.
Click the Dialog Normal Description text box at the top of the dialog. In the Text field, type Displays my welcome bitmap. This changes the dialog’s description.
Click the Bitmap button on the Dialog Control toolbar and use the cursor to drag a box on the dialog. Set the Height to 150 and the Width to 300.
In the File field browse to the bitmap file that you created in step 1.
After rebuilding the project (by pressing F7) and running it (by pressing CTRL+F5), the Welcome Bitmap dialog will appear after the Install Welcome dialog.
You need to edit the ResourceID (to something unique) in the Dialog table which is found in the Direct Editor under Additional Tools section in the Installation Designer.
By custimizing standard InstallShield dialogs, like sdWelcome, sdFinish and sdFinishReboot you will be able to use the dialogs default script APIs with the performed customization's
i want indentify all mouse click event like WM_LBUTTONDOWN and WM_LBUTTONUP, on picture control in vc++,
but i am not able to do this
please tell me how can i identifies all events separately.
thanks in advance.
You should enable property "Notify" of PictureControl to get the event.
You can add an event handler to the picture control using Visual Studio IDE and modify the code for handler function. That should be easy.
I'm guessing you're using MFC. In that case you have to add an activex control to your dialog.
i. Adding the control: To add such a control to your dialog box right click your dialog box and click the option called "Insert ActiveX Control". A modal dialog box appears. You have to select "Microsoft Forms 2.0 Image". Click OK. Control is added.
ii. Select an image: Right click your newly added control and select "Properties". Select your desired image clicking the picture attribute. Also there are other properties to customize the picture i.e, stretching, clipping image etc. You'll see your image is loaded into the control.
iii. Adding the handler function: Right click the control and select "Add Event handler". From the new modal dialog box select "MouseDown" or "MouseUp" as message type and click "add and edit". Add your code to achieve desired behavior.
N.B: MFC is not available with Visual C Express. You need a professional version of VS to compile MFC code.