mendixlabs / dropdowndivconverter Goto Github PK

It would be great if the button could have a dynamic title, like the standard buttons in Mendix

Hi, I discovered a bug on the widget. I'm using the widget to put my buttons, grouped together inside a table, and put it on a template grid. When I first execute the microflow, the parameter (grid object) exists and I can successfully execute my microflow. But upon second execution, the microflow's parameter is missing. So the microflow can only be executed once after the widget is created. Can anyone investigate this further? I am using Modeler 7.10.0.

I have updated the js so that the reset subscription updates the dynamic label.

DropdownDivConverter-master.zip

Hi,

I found this widget and think that it's awesome. But I wonder is it possible to trigger on click event with javascript and how?

Feature request from R&D UX to be able to select link styling / html instead of the dropdown button.

Trying to add a listview to the dropdown conatiner, in order for it to display a list of notifications.

Although the custom part of the widget itself doesn't use the method "applyContext" it somehow does seem to trigger an error:

Error: mxui_widget_LayoutContainer_0.applyContext: Error: DropdownDivConverter_widget_DropdownDivConverter_0.applyContext: Error: DropdownDivConverter_widget_DropdownDivConverter_0.applyContext: TypeError: Object doesn't support this property or method

When using the Split button dropdown with the second option, a microflow that requires an entity, I get an error if the microflow does not return an object. I can't understand why the microflow action should require a return.

Regarding this comment in the appstore

For people that have issues since MX 7.18, this is due to an implementation issue, not a bug in the widget. Please have a look at the following link:

https://github.com/mendix/DropdownDivConverter/blob/master/README.md#troubleshooting

When converted to Mendix v8.3 from v8.0 we encountered the above issue again although we already had the steps mentioned implemented and worked before.

a fix for this was adding a additional container to the suggested implementation structure so ours now looks like this.

• Container
  • Container
    • Container
      • Element for dropdown
      • Element for dropdown
      • etc
    • DropdownDivConverter

Since MX 7.18 the widget gives the following error:
Unable to destroy:: Error while uninitialize NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

The error only occurs when there's an object in the container. If the container is empty the error does not occur.

Hi!
There are small bugs with the link:

• The label is http://http://bootstrapdocs.com/v3.0.2/docs/components/#btn-dropdowns and should be
  http://bootstrapdocs.com/v3.0.2/docs/components/#btn-dropdowns
• The link is http//bootstrapdocs.com/v3.0.2/docs/components/#btn-dropdowns and should be
  http://bootstrapdocs.com/v3.0.2/docs/components/#btn-dropdowns

Cheers

We created a message box with the dropdown converter with a notification at the top of the message box to indicate the amount of unread messages. When opened, the DropDownDivConverter triggers a microflow that marks all unread messages as read.

However the microflow also triggers on login, probaly due to the rendering of the widget, which causes the message notifications to disappear on login.

Is it possible to fix this, so the microflow only triggers when the div is opened?

If a Mendix widget like a listview has an onclick behaviour it prevents the dropdown menu from closing.
This is caused by the event propagation stop behaviour of the Mendix widget.

This needs to be fixed by adding a (target phase) event listener on the dropdown menu. (and removing it on killing the widget.

Hi,

We have the dropdowndivconverter widget placed on static Entity detail page, say Task_View. In the menu we have buttons with conditional visibility according to the EntityStatus (ie. to-do, doing, done).
Each button sets the 'next' status and does a refresh in client from the microflow.
At this moment after the refresh the user is presented with an message "An error has occurred that might have been caused by fast reload. Refresh the page to fix it." If you press cancel instead of refresh, the menu contains the buttons for the old status and the new status, and the buttons for the new status have a additional class 'disabled'.
In the console we see the error "Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node. Error: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node."

The widget is set to self-closing and has no context object, although we tried without self-closing and with context object as well. It is the last child in the container.

The current workaround is to close the page as action in the microflow and then open it again.

Hello, I hope you could help regarding my below requirement. We were trying to create a dynamic dropdown menu but we having a issue on showing it in dropdown. I've attached the screenshot of the work and the output. Thanks in advance.

A regular microflow action button has settings for 'disabled during action' and progress bar settings. It would be great if these were also available when using the split button dropdown settings. At present these settings cannot be set for the default action. For complex actions, not having the blocking progress bar can be a problem.

The standard option for closing the Drop Down menu is not working if there is a visibility condition set based on attributes value.
Whenever I set the visibility of the drop down values on 'Always’, then does the Close Menu work properly.