I am trying to integrate Glimpse into my existing ASP.NET MVC 5 project. But I cannot see any HUD at bottom right corner as demonstrated in their site. I have all of the assemblies downloaded from NuGet, using Visual Studio 2013 Ultimate and running in localhost.
Can anyone tell me what could be the problem? I am not finding any relevant topic online either.
#Md.lbrahim by looking at the comment replies of you above, it seems that Glimpse is indeed active and rendering its <script> tags.
Can you check with the browser developer tools whether the Glimpse client is actually rendered at the bottom but maybe hidden by another element that has a higher z-index?
If you still can't get the HUD to show up, then maybe create an issue on our issue tracker and try to provide as much details as possible (browser used, versions, other installed packages that might interfere with Glimpse rendering etc...)
Related
After Summit 2019, we were excited to start working on updates for 2018R2, and I practiced adding mobile screens for our custom modules in my sandbox.
We decided to fully refresh our DEV instance and reapply our customizations. No problem there, but when I try "Add New Screen" in the mobile section and then try to enter my screen number, the mouse goes to "waiting" and I can't add my new screen. Eventually, I get a "timed out" message. Same problem even when trying to add a standard Acumatica screen. Everything else in the project and Acumatica web interface seems to work fine.
Any ideas on where to look for what is preventing adding a new screen?
I'm on Build 18.209.0021.
It seems like an Ajax issue in the customization project editor. After callback to server the client page javascript is stuck waiting on the server response. You can try using Chrome browser which has less of those Ajax hangs and update Chrome if you're already using it.
There is also a known issue specifically affecting 2018 R2 Mobile that leads to generic error Sequence contains no matching element on mobile detail page. Based on your question this doesn't seem to be the issue you are having but you can give the workaround to this bug a try:
Open Generic Inquiry screen (SM208000)
Select FS-ServiceOrder inquiry, uncheck Expose to mobile and save
On Apply Updates screen (SM203510), click on Restart Application
This was identified by Acumatica support as a bug. Upgrade to a new release for the fix.
Last week I tried to update my Notes client installation from 9.0.1 FP9 to FP10 IF 3. For technical reasons I had to roll back which proved to be quite difficult, and I ended up completely uninstalling Notes and doing a fresh installation of 9.0.1 (standard) then FP9 IF 2.
Everything's fine (and much more responsive than before, too) with one serious exception:
Within the client help popup window for Notes client and Domino Designer help is hardly usable now; obviously there's no CSS style or whatever applied to the nav page / frame:
As you can see in the screenshot styling of the main window part (green frame) is fine. But everything that is releated to navigation (red frames) appears to be raw html. Javascript calls are apparently working but it's really hard to navigate the "chapters". Same applies to Designer help, of course.
Here's what I tried to solve that riddle:
uninstalled and re-installed full client 3 times; sometimes I ran the
installation as local Admin other times I didn't (no difference)
just installed plain Notes 9.0.1 from scratch then tested Client help before updating to FP9IF2 (no difference)
restored the entire [Notes-Programm]\framework directory from a
backup I took when Notes help still was working as expected (no difference)
copied over the entire \Notes\ folder from a different PC where popup help is still working fine (no difference)
Problem with that is: being a Developer I need to have a functioning help window in my Domino Designer. The navigator as it is right now however is plain useless. And designer_help.nsf isn't of help at all when it comes to Java, LotusScript etc. objects and classes.
One of my co-workers has the same phenomenon while another one hasn't.
Question: did anyone else experience something like that? Where you able to solve it? How?
This seems to be related to an issue with the embedded browser windows that Domino Designer uses to open the Help website.
Try to open following link in a modern browser (such as Chrome or Firefox) and the navigation should be fine.
http://localhost:50970/help/index.jsp?topic=%2Fcom.ibm.notes.help.doc%2Ffram_getting_started_c.html
Bookmark it and use it when you need it.
Try using the IBM Nice tool to see if it can fix your issue
https://www-01.ibm.com/support/docview.wss?uid=swg21459714
Meanwhile I restored my entire Windows system partition from a backup created just before all that began (lucky me that I have both regular local backups plus a separate system partition). And that finally helped resolve the problem.
Meanwhile I'm 99% sure that this is due to a rather new registry and/or firewall setting not yet known to IBM's NICE tool.
I try to use dropzone.js in my project. I implemented it excactly according to this example. I am totaly pissed off because after drag and drop the files are uploaded however the page is refreshed and the preview images disappear. Did anyone meet this problem?
Maybe my question deserves downwote but I hope this answer saves someone from the same struggle. After a little research I found that the problem causes new visual studio feature Browser link. For some reason after successful image uploading browser link invoked page refresh so ofcourse I lost image previews. This was unexpectable behavior.
I added a couple of custom control into a plugin and imported them on the server using the update site. They are working quit well so far but when i open an application in the designer client i can see the custom control from the plugin twice.
I tried to add them the same way bootstrap4xpages is adding a plugin but mine is duplicated.
One entry is without any icon the other has the standard grey cc icon. Not the end of the world but i must have done something wrong. Any idea why that happens?
It's a known issue with 9.0 and 9.0.1, specific to components that are Custom Controls. I encountered it quite a while ago. Mark Leusink had the same problem for Debug Toolbar and discussed it with the IBM developers at IBM Connect last year. So I would hope it will be addressed in the next point release, 9.0.2.
It still works fine though, regardless of which one you select.
Something weird is happening.
My Silverlight applications for CRM 2011 are missing their default loading splash-screens.
I can create a simple Silverlight app without setting the RooVisual element...
//this.RootVisual = new MainPage();
which will create an "endlessly loading" effect. Normally, if I run it via the debugger or host it in an IIS, it's as you'd expect: I get the typical SL loading indicator. However, if I place it in CRM 2011 web resource (doesn't seem to matter if it's a local CRM installation or online) and use that as part of a form, I just get a white rectangle.
Now, so far, all my SL controls are used in local installations, so loading times are non-existent. However, I'm creating a solution which might end up being used on-line, and leaving it as it is, a client could think the application has hung-up or crashed while in fact it is still downloading.
I've also tried using a custom splash-screen, with the same results.
What could possibly be wrong? Is this some documented (or undocumented :P) CRM feature that I missed?
Well in our CRM 2011 environments they always show the Silverlight loading screen, so I'm not sure why they aren't displaying for you.
Have you tried just a generic 3rd party silverlight application?
One thing you could do is have an HTML web resource that has a loading screen on it and then using your silverlight application hide the loading screen (which it will do only after it's loaded).
I've solved it!
The issue, as it turns out, is naming the CRM resources with a .xap on the end, for example new_mySL.xap.
I could swear that we didn't do it in our older projects and that the splash screens worked correctly... as such, I don't know if there was some CRM update that changed this or perhaps my mind is simply playing tricks on my (quite possibly the latter).