I have developed quite a few InfoPath forms in my life, but I only recently started developing with InfoPath Designer 2013 and I am coming across a very peculiar "bug" (I don't know that it's a bug for sure) indeed.
The form opens fine to design but when I change a field's name, for instance, the application stops reacting in certain areas. The InfoPath toolbar doesn't react at all except for when I click FILE (which opens up the little menu that's supposed to open when you click on the InfoPath icon in the very top left corner). In addition, I can also right-click on the elements inside the form to open some of the properties of the elements; however on the right side of the screen where the fields and groups are listed, nothing reacts either.
I have tried to find this on Google and I was quite surprised that it didn't seem like anyone else had asked about this; however that seems to be the case (although I'm hoping not). Please note that InfoPath stops reacting only after I change the field or group name.
Does anyone out there have any idea as to what might be causing this?
Thank you and regards.
Hermann
I have this problem too. The only workaround I've found is to Alt-F, Save, close InfoPath, reopen InfoPath, then reopen the document.
Related
I'm hoping this is just a simple pointer to something existing which I couldn't locate via google.
What our business folks want is a button much like the "Open" button which once clicked, gives a pull-down with 3 options. I can't quite figure out how to pull that off.
I can easily add a button. I can even add a stack of 3 "small" buttons vertically. I can't quite figure out the drop-down from large button. One of our folks thought he did this a long time ago, but can't find any evidence to prove it. ;)
Can anyone point me to what I missed? or, anyone confirm that it's not possible?
thanks,
~Warner
Unfortunately that is implemented in a different way than how normal buttons are added to the ribbon. I am basing this on the answers I received here:
Is it possible to remove the "Upload MM Component" button from the SDL Tridion 2011 Ribbon
It seems you will need to create an ASCX to achieve this.
Whenever you are in design mode in VS2012 for editing a Web Form, if you click on anything, and accidentally drag and drop, a CSS auto-style will appear at the top of the HTML for the aspx page.
From some preliminary research, I checked the following:
Tools>Options>HTML Designer>CSS Styling>Style Application Mode, but it was already set to manual. Is there somewhere else I should be looking to disable this functionality?
Right now there is no way to turn off this. We have received this feedback through connect link. Please add vote to this connect bug. And we will consider this in future release of VS.
I also found this, and I have assoicated it rightly or wrongly, with large pages getting totally corrupted (table cell contents being apparrently randomly swapped).
I managed to turn autostyle off by going to Tools>Options>HTML Designer>CSS and selecting 'CSS (inline styles)' for each of the items there.
Autostyling has stopped and (fingers crossed) my latest pages have retained their integrity.
Tools > Options > Web Forms Designer > CSS change all CSS(classes ) to CSS(inline styles)
We have an application running flex sdk 4.5 and have recently encountered an issue with textInput fields which we have not been able to reproduce on our end for the better part of a month now.
Here are the symptoms:
Users opens an input form which contains several input fields (combo boxes, calendars, text inputs, etc)
User clicks inside a text field
Users types (obviously!)
** Nothing appears in the text input - we have validators on some of these fields and they do kick in properly (ie. user sees red box around textInput disappearing)
User moves cursor outside of text input field and text appears
Give or take, this is the test case we've been provided. We have been unable to reproduce this and I'm reaching out to see if anybody has heard of issues like this in the past.
They are running our flex application in the following environment:
Windows XP SP3
IE 7.0.5730.13 (locale = en-gb)
Flash Player 10.3.181.14
Upgrading either of these components is not an option. Installing the flash player debugger is not an option either.
Now we've setup a pc exactly the same way as they have on their end and still haven't reproduced. So we're really stuck at this point :)
Any suggestion is greatly appreciated. I'll provide any additional info needed.
-Marc
Feb. 2nd 2012 - Update
As I noted in my comment reply to shaun, it seems our customer was more or less precise in their description of the issue. We ran a webex session with them this morning and actually saw the issues first hand.
Here's what happens:
- User loads our application via its url
- User is able to input data and pretty much do any function for a 'random' time period
- All of a sudden, the issues start (there are more symptoms than just the one I originally mentioned):
1. Users type in text input fields and they won't see the text appear until they move the cursor out of / into any other component (could be entering an hbox, exiting a text input field, etc)
2. Combo boxes behave more or less the same. They can drop them down, but then the mouse wheel no longer refreshes the list. It actually scrolls in the background, but until the user moves the mouse, the list does not refresh
3. We also communicate between the server and client via an amf channel. The events make it to the client, but again, they won't see the screen refresh until they move their cursor.
So basically, the application still seems to work, but the screen is no longer refreshing. Could it be something to do with an invalidate / update of the display list that doesn't kick in? We'd like to get them to install the debugger version of FP, but that doesn't seem to be an option.
Another thing to keep in mind: they have a VERY bad internet connection. They average around 1-1.5mbps (megabits) which is enough for our app, but I just thought I'd let you know.
We learned that they also use a Citrix presentation layer to deploy IE 7 to the end users. We've received confirmation from the end user that even if they launch IE on their workstation (not through citrix), they get the issue also.
Another note is that we've seen no errors in our web server, jboss or application logs...
So that's the update I've got... anyone have more thoughts on this? We've more or less discarded the fonts being an issue at this point since the issue affects more than just 'fonts'. Is everything on the screen not updating anymore.
I'm having problems making FullCalendar fully accessible. I'm using the default month view and can't access the next, previous, and today buttons on the top right without using a mouse. If I run a screen reader, I can access those buttons but not without running the screen reader.
And on another note, I currently am using tool tips that pop up when you mouse over an event title to display more information. If anyone has any tips on how to make those accessible to a screen reader or accessible without a mouse, I'd greatly appreciate it!
Regarding the buttons, I would advice that you write new buttons if accessibility is important. These buttons you could then hook up to your own javascript functions that moves to previous and next.
Check out this documentation example
Regarding the second problem, I think that's the same problem not just for physically impaired but also for things like mobile browsers. My tip would be to avoid onmouseover if the information that appears is really important.
Can any one tell how to disable focus to a browser.
Hi i am currently working in .net application and i need to disable the tab focus to browser objects such as toolbars,address bar, since the user will not be using these components often
Thank you
Please don't do this, it breaks what the user expects a webpage to do. Messing with the fundamental behavior breaks several things:
My tab button and where I expect it to go
Screen readers for the disabled
Trust in your application
In some cases, you need to ask why? before asking how?, this is one of those. Anything that behaves differently from the other 99.9999% of the web is broken in the eyes of your user.
Well, I agree with Nick Craver. If you have to disable due to some crap requirements, then try opening a new window without toolbar, editable address bar etc and load the page inside the newly opened window.