Problems with SELECTION_CHANGED_ EVENT in Forge Viewer v7* - treeview

I have a problem when I upgraded Forge Viewer from v6* to v7* with SELECTION_CHANGED_ EVENT, everything is working fine if I select the object from the Viewer, but when I select the object from the Model Browser the getSelection method returns empty.
This works fine in the v6* but not in v7*.

The model browser behavior has changed in v7. You'll notice that clicking an object in the model browser now isolates it instead of selecting it. So, for your original use case, consider listening to the Autodesk.Viewing.ISOLATE_EVENT event, or to the Autodesk.Viewing.AGGREGATE_ISOLATION_CHANGED_EVENT event.

Related

Outlook VSTO - ActiveInspector returns the incorrect contact window's information

Globals.ThisAddIn.Application.Explorers.NewExplorer += new ExplorersEvents_NewExplorerEventHandler(DoNewExplorer);
I am trying to get the information from an email that I previously opened (by double-clicking) in outlook.
The code works fine until I open multiple emails. What I am finding is that when I click on an email, the inspector activates, but I am getting the information from the last active window, not the current one that I clicked on.
In the Activate event handler you can always call the ActiveInspector method of the Outlook Application class.
Note, the Inspectors collection contains all opened inspector windows, so you could get all of them or find the required one.
Firstly, your code tracks the Explorers.NewExplorer event, not Inspectors.NewInspector.
Secondly, for the Inspectors.NewInspector event, make sure you are using the Inspector object passed to your event handler rather than Application.ActiveInspector: by the time Inspectors.NewInspector event fires, the inspector might not yet be visible/active.

Missing GA4 event parameters

I have recently started to use Google Analytics 4 for event tracking, using Google Tag Manager to send events to Analytics. I have set up the custom variables in Tag Manager as well as in GA4.
Everything seems to work very well in Tag Manager's debug mode, and also if I look up the events in real-time view I get the requested event along with all the parameters I have set in Tag Manager. However, once I look up the events for the last couple of days in the Engagement -> Event view, a couple of my parameters are missing, and also I'm not getting the same hit count for each parameter, even though each event has all parameters set:
As you can see, 86 events have been recorded, but the event count for the parameters widely varies.
Here's a screenshot of my Tag manager settings:
I have tried to set up a new event with the same parameters, but (logically) I got the same result. I am under the strong impression I'm missing something obvious here. Does anyone have experience with this, or has anyone come across this same issue?
To be honest, you can just try to click on mark as conversion in the Events tab, and this should save them. I think for some reason GA4 doesn't save parameters otherwise...
i cant get this til work with fields and parameters for an event so i try to create a user custom dimension instead and also to send it as a content group and as user property
also i can see the user id under app instance for the standard report user explorer
but i can't filter on or select this one myself
i cant create the custom parameter reports like gerrit did
but yeah create them as custom dimensions /metric first should be the way
ga4 has a bug when you edit a standard report, you add 3 card and deselect one it still thinks you are maxed out and you have to start over...
the test internal users filters dont work, though you can see data in debug and under events, but since i know they work i know try to just make the filters active

Addind and removing UI elements in restartless TB addon

I develop a restartless addon for Thunderbird. I need to add some UI elements in compose window when the addon is activated.
What I did so far is:
at startup, add an observer on windows via nsIWindowWatcher
at shutdown, remove window observer, and set a variable X to true
when this observer observes domwindowopened event, add a eventlistener to the opened window for "compose-window-init" event (when it observes domwindowclosed, it removes the eventlistener)
when this compose-window-init event is fired, check the document.location of the window, if it corresponds to a message composer:
add the UI elements,
or remove UI elements and remove eventListener, if X is set to true
This works well (UI is added to compose message when addon is activated, and removed when deactivated) except the following : when addon is deactivated then activated again, the first compose message is not provided with the UI elements. The UI is added to the other one, but not to the first.
Any idea on why and how to solve this ?
Thx
I found what was wrong.
See my post at:
http://forums.mozillazine.org/viewtopic.php?f=19&t=2949755&p=14254205#p14254205
Regards

Different behaviour for local and productive WeblogicServer

.
Hey guys,
I have a strange behaviour and am wondering why this happens:
My managed bean holds three values (selected plant, selected year and selected month). When opening the required page a #PostConstruct method is called and initializes the plant data according to the selected/pre defined plant, year and month. When changing one of these three options data should be updated and displayed via AJAX request. In order to switch to edit mode I can click my button and change one value from true to fals which is indicating whether the page should be displayed in view or edit mode.
Now here is my problem:
My local Weblogic Server (IntegratedWeblogicServer - standard configuration) works as expected. I open the page, see my current data, switch to edit mode, edit & save it. That's all. Works like a charm.
The productive Weblogic Server (configured by a colleague of mine) does some kind of cache I think. I open the page, see my current data, change year value to last year and see the updated values. When clicking on the "edit" button the old values are displayed instead of the updated values. This just happens as long as I do not switch the plant. My current workaround looks like this: open the page, switch the plant and then switch the year. After switching the plant everything works like expected. I can't figure out why the productive machine behaves different than the local machine. Each of the update methods setPlant(), setYear() and setMonth() call refreshValues() and are equal requading JSF definitions. So I don't know if it's a caching problem or maybe a Weblogic configuration problem.
Let me know if you need more information or certain code snippets. I excluded them as it is a lot of code.
Kind regards,
Stefi
Enable http headers debug from browser and monitor the difference in each environment. Also monitor the access.log on each domains server.

Microsoft Dynamics CRM 4 custom entity form onload event not firing

We have a problem with the onload event of the form for a custom entity not firing. The form did work correctly for a period but recently has stopped working. Now none of the code in the event is executed when the form is opened - either when creating a new instance of the entity or when opening an existing one. The code does however get executed when the form is previewed.
For testing purposes the original code has been removed and the onload event currently only has the following:
crmForm.all.ownerid_c.style.display = 'none';
crmForm.all.ownerid_d.style.display = 'none';
alert("OnLoad event fired");
In preview the Owner attribute is hidden and the alert is shown. When running the form normally the attribute is not hidden and there is no alert (there are also no Java errors reported).
The full CRM version is 4.0.7333.1219. The entity was originally created on a different CRM installation which was initially version 3. That environment was upgraded to version 4 before we did the export – import process for migrating it to the current environment. The form worked correctly for a period of time on the new environment but at some stage stopped doing so.
I enabled platform tracing using Microsoft Crm Diagnostics Tool 4 and now the onload event is executed. It still works when tracing is disabled again.
God I love developing in this environment.

Resources