[FeedbackMessage++] Feedback message does not show when navigating away from screen

[FeedbackMessage++] Feedback message does not show when navigating away from screen

  
Forge Component
(8)
Published on 2016-05-19 by André Siébra
8 votes
Published on 2016-05-19 by André Siébra

It turns out the feedback message does not show when, after the message is issued, the navigation flows away from the screen. 

See my demo page for the difference between the original Rich Widgets and the new FeedbackMessage++ solution. 

Click on the right upper side buttons that will show a message. Check the Stay checkbox to stay on the screen, and leave unchecked to navigate to another screen. 


Hi Peter,

This is probably a bug with the script flow... I'll check this out as soon as possible. I'm planning to publish a new version next week with some fixes.

Thank you for the feedback!


Cheers,

André Siébra


Hi all,


Would be nice to see this fixed indeed.


Kind regards,

Evert

Dear André Siebra,

Congratulations on the component, I am using in my projects, already have a solution to the problem of not being displayed when you navigate to another page?

Best regards

Huarlem Lima

Huarlem Lima wrote:

Dear André Siebra,

Congratulations on the component, I am using in my projects, already have a solution to the problem of not being displayed when you navigate to another page?

Best regards

Huarlem Lima

Hi Huarlem! I'm glad you are enjoying the component. 

Sorry, I could not find a solution yet. Currently I'm very busy with a project I'm working on... so I had to postpone this fix. I hope this weekend I will fix this out. 


Cheers,


 


Hi André, 

Looks like you are still very busy with your current project, since it has been two months since the latest reply. Do you have any idea when you will be able to work on this wonderful component again?


Kind regards,
Peter



André Siébra wrote:

Huarlem Lima wrote:

Dear André Siebra,

Congratulations on the component, I am using in my projects, already have a solution to the problem of not being displayed when you navigate to another page?

Best regards

Huarlem Lima

Hi Huarlem! I'm glad you are enjoying the component. 

Sorry, I could not find a solution yet. Currently I'm very busy with a project I'm working on... so I had to postpone this fix. I hope this weekend I will fix this out. 


Cheers,


 




Hi Peter!

yeah... sorry for the late but I'm really very busy, but it's getting better (I hope). One day I was working at it and unafortunately I have bad news... 

This component basically overloads the implementation of the original Richwidgets Feedback Message. So there's some limitations when working with it. I took a look at the problem of not being displayed when navigating to another page. I realized that the Richwidgets' component uses Session variables to store the message info to allow showing it at another page. This logic is in the WidgetsForLayout webblock that is placed inside the Layout. 

It works like this: when you call feedback message action it stores the message in the session. So when you navigate to another page, the layout preparation verifies if this session variable is filled and displays the message.

I can handle the javascript to change the way how the message is displayed, but I can't assign the message to a session variable that exists in another espace (Richwidgets). I've tried a lot of ways, but without success.

I'm still trying to find a way to overcome this... if you guys have any idea, I would appreciate a lot!

Cheers


Can an extension access session variables outside it's own espace? I would think that a .net extension for example could set and access any current session variable so creating a small extension specifically to set session variables may be a way round this.


Hi all, 


There is a new version of this widget. 

It has suffered some big changes to enable the messages to be stored in session, just like Richwidgets does. 

Just check it out and try to see if it performs as you want. 

Also added some new methods to be provide better readability and ease of use. 


Hope you like it.

Great work José, will give it a try as soon as I can.


Great work, José! 

First impressions are pretty good, using the new version in my small trial eSpace. 

Remarks: 

  • the component references an eSpace BPL_Theme, which I don't have. It doesn't seem to bother the implementation, so maybe it can just be cleared from the component. 
  • the Helper functions are great, but why not use the same input parameters (aside from the MessageType) as are being used with the FeedbackMessage action? 
  • maybe the ManualClose parameter can be added to the FeedbackMessage action?
  • you might consider using site properties to set some default values for Timeout, HideAnimation (so they can be used by the Helper functions as well) and ManualClose, although the last one should probably have a simple False as default as a parameter. 

When I have more time, I will try to run some more tests. 

Regards, Peter

Two extra remarks after first tries: 

  • When using HideAnimation = SlideToggle, the message "toggles" (rolls over and gets displayed again) but doesn't hide after that
  • When using HideAnimation = Drop nothing happens and the message can only be closed manually. 


Peter

Peter van Munster wrote:

Great work, José! 

First impressions are pretty good, using the new version in my small trial eSpace. 

Remarks: 

  • the component references an eSpace BPL_Theme, which I don't have. It doesn't seem to bother the implementation, so maybe it can just be cleared from the component. 
  • the Helper functions are great, but why not use the same input parameters (aside from the MessageType) as are being used with the FeedbackMessage action? 
  • maybe the ManualClose parameter can be added to the FeedbackMessage action?
  • you might consider using site properties to set some default values for Timeout, HideAnimation (so they can be used by the Helper functions as well) and ManualClose, although the last one should probably have a simple False as default as a parameter. 

When I have more time, I will try to run some more tests. 

Regards, Peter


Hi Peter, 

Tanks a lot for the feedback. 

That reference is now removed from the version 2.0.1, I forgot to clear all unused stuff from the espace before uploading it. 


Actually the helpers I confess I did them just because the seemed to be handy to me like that, but I agree, I might just apply the same input set as in the other feedback and leave it with default behaviour. 


Regarding animations

This is also something I changed in the component, if you look into the Feedback_Message_Proxy webblock you will find the following javascript functions in the JS sections of the webblock:

  • animateFeedback (element, animation)
    • Function that defines each animation behaviour in jQueryanimation ;
  • hideFeedback (timeout,animationName)
    • Function that defines the way it calculates the time for hiding the feedback; 


Now this two functions are global scope functions. You can even use the animateFeedback as a standalone animation to hide some elements in your applications. 

That said in terms of animations you can always wrap around this webblock and overwrite them to meet any special need or desire for your projects. 


If you find the correct jquery animation to display in the cases it is not working that great please share with us and I'm happy to incorporate better behaviour in this component. 


Regards, 

José



José, 

I agree on the helper functions, I had already made similar ones, because it seemed useful to me as well   

I made different icons though, all variations on the component icon, only varying in color to indicate what type of message is being issued: Info=blue, Success=green, Warning=orange, Error=red.

That way the action icon is always identical, so it's clear that at that point a FeedbackMessage is being issued. 

Peter