nexuni / famcy Goto Github PK

No error from frontend and backend
Web result:
{"indicator": true, "message": "error_event trigger action"}
Backend result:
famcy_docker_carpark-nginx-1 | 10.0.0.1 - - [13/Aug/2022:01:36:51 +0000] "GET /overview/led HTTP/1.1" 200 58 "-" "python-requests/2.27.1" "-"
famcy | overview_led___ Save to session current_page
famcy | INFO:werkzeug:172.19.0.3 - - [13/Aug/2022 01:36:51] "GET /overview/led HTTP/1.1" 200 -

Ex.

input_form.layout.addWidget(restart_btn, 2, 4)
pcard.layout.addWidget(input_form, 1, 0,1,2)
pcard.layout.addWidget(change_remaining,0,0,1,1)
pcard.layout.addWidget(receipt_remaining,0,1,1,1)

Ifa function update layout.content[0][0].layout.content[0][0] content, could not move the addWidget position

Ex. http://10.0.200.184/overview/error_log
Use Postman to send {"error":"OK"}
-> Could get data from the API style {"error":"OK"}

def error_event_action(self):
self.event_trigger_task1.associate(self.error_event_, info_dict={}, target=self.card_2)
Famcy.sse.publish({"indicator": True, "message": self.event_trigger_task1.tojson()}, type='publish')

If there is something that I would like to update both in card_2 and card_4, very inconvenient.

            "page_footer_detail": {
                "page_size": 10,
                "page_list": [10, "all"]
            },

Strange behavior when clicking on page_list button

Table Fblock not work

When getting input form data from the submission objects, we need to do info_list indexing and this is not scalable. So, we need to add labels to make the access easier and more prune to change of code.

The issue being that the login process failed to proceed and the loader spins forever after the latest event source update (0.3.17)

1. If website idle (no user control for more than 1 hrs), automatically logout
2. One login session should only remain for 24 hrs

===============
Either one will be ok, but prefer the first one more.

The problem being the custom login manager won't load the new list of user data after registering new users. Also, it seems not reasonable to keep all the user data in the class objects, need to think about this portion in the future if large quantities of user data is generated. We can keep this for now since we are focusing on management console.

Situation

self.card_2.layout.content[0][0].layout.content[0][0].update({"data": Famcy.FManager['error_log']})
Before Update the table 4 row of data
After Update the table 6 row of data
I have a function which will change the color of the table. I should loop through 6 row of data. However, the data not yet update, so there will be only 4 rows. This will cause [i] list index out of range.
Add postload for evernt source might help this question.