I use a modalService ie. NgbModal to submit the Form on server. This form is having like 50 to 60 fields.
When the form is submitted multiple times then after few submissions the website becomes extremely slow - like unable to type anything, dropdown does not show up etc.
The issue has only been with modals, if same form submitted on pages then this works fine.
I have tried debugging the code using Augury but I believe Augury does not show up the entryComponents
This is how the modal is open.
const modalRef = this.modalService.open(AddOrderComponent,this.modalOption).componentInstance;
//Closed.
activeModal.dismiss('Close click')
The issue was with one of the setting for adjusting the layout RTL to LTR. A function was executing again and again. I managed to resolve this with the help of Chrome JavaScript Runner tool
Related
I am using Maximo 7.6.1.1 and Birt (eclipse 4.3.1). The requirement is to add some page related text with a field from the report into the footer on each page, so I am attempting to update the master page footer. The master page is local, not extended.
I have tried to repeat this from 2013 (https://www.youtube.com/watch?v=lw_k1qHY_gU&t=4s) without success.
So using page level variables as described by the link did not work - it appears that the page event for the variable I chose (when the variable is about to be updated on the page) did not seem to be getting invoked.
Has this possibly changed (since 2013) or does someone know of another work around?
I tried to add a number of data elements to the footer without success.
I did see that if I added a value to the footer element in the initialization event for the report, that we could see that but we never got any updates even though the field we wanted to use was updated as it is normally.
I don't know Maximo, but these page variables only work if BIRT is running in 2 steps: RunTask, then RenderTask. If the program is using the single-step RundAndRenderTask, page variables don't work. This behaviour has not changed with "newer" BIRT releases.
I am using Delphi XE2 and Chromium CEF4Delphi. I am trying to use a web page via the TChromiumWindow component and would like to detect when an element is selected / clicked.
I saw this post..
Delphi Chromium - launch a command in Delphi application when button in web page is clicked by user
Unfortunately, I cant find the function AddEventListenerProc in the CEF4Delphi library. Neither can I find an alternative way to monitor a button / element click.
I would like to use the TChromiumWindow component to act as a "fron-end" to my app and would like to monitor user button clicks etc.
Can anyone help please ? I did try the developer forum but I dont see much activity there and was unable to register.
Many thanks..
The DCEF3 project has a group here : https://groups.google.com/forum/#!forum/delphichromiumembedded
But the CEF4Delphi and OldCEF4Delphi projects have a developers forum here :
https://www.briskbard.com/forum/
That forum has new posts almost every day and I try to answer them as soon as I can, usually in less than 24 hours.
If you have problems creating an account just send me a message and I'll activate your account manually.
The link you posted is very old and many things have changed in CEF since 2012.
There are several ways to detect when a HTML element has been selected, clicked, etc.
You can use a JavaScript event like "onclick" that calls a custom JavaScript extension. That extension would send a process message to the browser process to notify that the user clicked that element.
You can also use the GlobalCEFApp.OnFocusedNodeChanged that is triggered when an HTML element has been focused. This event is executed in the "render" process so you will also need to send a process message to the main browser process that the focused element has changed.
Use the JSRTTIExtension or the JSExtension demos as a template for your app.
They show you how to set a "mouseover" event that calls the "myextension.mouseover" function defined in a custom JS extension. The myextension.mouseover function executes Delphi code and sends a process message to the main browser process with some HTML information that is shown in the status bar.
They also have an example for a "MutationObserver" that calls a generic "myextension.sendresulttobrowser" function in the JS extension that sends the "value" attribute to the browser process.
Build the demo and right-click on the web page when it's fully loaded. Then select the "Set mouseover event" or "Add mutation observer" options to test what I described.
Update It appears I have to rebuild/redeploy the app to see the changes. Anyone know why I have to do this? It's a static .xhtml page. Coming back to update, looks like I just have to stop/restart the server, not a rebuild. I was dumb and didn't try that first, mostly because I have to rebuild/deploy often anyways.
I'm working on a JSF 2 app that uses f:subviews. I'm on one subview where my changes aren't reflected in the UI when I refresh the browser. I've worked on other subviews where I don't have this problem.
I have a batch script which copies my .xhtml files into my installed apps folder. The batch script reports the file is copied over. It's business as usual... If I drill down into this particular installed app, I see my change in the file. Again, seems like business as usual. The change is not reflected in the UI when I refresh, however.
These are simple text changes I'm making, but not seeing.
The problematic subview doesn't appear to be anything special, it's just a p:datatable that's included via a ui:include with a couple of parameters for the data and to give it a unique id. If I replace the p:datatable with just simple text, the "old" table still shows up in the UI when I refresh. I just can't get any changes in this subview to be reflected in the UI.
Console doesn't throw any errors.
I'm using WebSphere 7.0.
Never encountered this problem before. It isn't a browser caching issue as I can edit other subviews and see those changes when I refresh the page.
Anyone have any ideas?
I have an xul overlay based Firefox Add-on that works. It has inline options defined in content/options.xul and they display/function correctly when the user goes to Firefox->Add-ons->Extensions->{The Name of My Extension}->Options
The question, can I a create a button on my Add-on that will launch my options either by taking the user to Firefox->Add-ons->Extensions->{The Name of My Extension}->Options with one click or by launching a dialog based on options.xul?
Right now I am maintaining a separate options.html and options.js that gets and sets the same settings that options.xul handles when the user navigates there via the Firefox button but I would much rather dump options.html and options.js and only maintain my main.js and options.xul.
Any comments or code examples will be greatly appreciated.
This is easiest to do via a global function BrowserOpenAddonsMgr() defined in the browser window, like this:
BrowserOpenAddonsMgr("addons://detail/" + encodeURIComponent(addonID));
This function takes care of focusing the existing add-ons tab if there is one or opening a new tab. It will not scroll down to the options however which is an issue if the add-on has a lengthy description. Starting with Firefox 12 this can be solved by adding "/preferences" to the view identifier:
BrowserOpenAddonsMgr("addons://detail/" + encodeURIComponent(addonID) + "/preferences");
With older Firefox versions you are out of luck (and you shouldn't use this suffix there, it won't work). The other issue is that there can be a lengthy "loading" phase where the add-ons manager fetches metadata for all extensions.
I'm building a form in the Orbeon Form Builder. The simplest way to recreate this problem is as follows:
Put a control on the form.
Give it any label, it does not matter.
Go to 'control details'.
Change the 'Control Name' to 'test-controlenummer'.
Confirm with the 'apply' button.
See the control itself disappear
Notice that the question mark of the help feature does not disappear, nor do the delete and validation options once you hover over the formerly-visible-component. The grid cell also acts as if it was occupied. The control simply does not show and some of the changes to the name and/or validation options result in XPath expression errors.
I have taken a quick look at the underlying xml code, however at first glance I did not find anything out of the ordinary.
It disappears because of a bug in Orbeon Forms 3.9 when control names contain a dash. Like you said, there is nothing wrong with the markup Form Builder generates, but it then incorrectly just doesn't expect a dash to be present in the control name.
This bug has been fixed in the latest code, so it won't be present in the next release.
If you are using Orbeon Forms PE, I recommend you contact Orbeon to see if you can get a patch for this (either through Basecamp if you already have a support account setup, or by email, info AT orbeon.com).
If you are using Orbeon Forms CE, for now, you can work around this issue by avoiding dashes in the names of your controls.