I want the the same like chatgpt does you create a new chat and after chatting there is a subject created about what you were texting so yes i want to keep the threads but i want the chat always to be visible
So the process for that is to either create a thread then go to the thread page then create a chat or create a chat that is not associated to a thread and then you can later add the chat to a thread. You would need a redesign. So in chat chatgpt you basically have two repeating groups on the left. One for a list of threads, one for a list of chats. This is what I would do…
Create a new page with two short lists. One is a list of threads, one is a list of unthreaded chats.
Two buttons, create a thread, cread a chat.
Create a thread workflow:
Create a thread button clicked -
Create a thread (name, icon, user)
Send data to threads page results of step one
Go to threads page
Threads page is a list of this threads chats, one button create chat
Create chat for this thread workflow:
Create chat clicked -
Create new chat (user, message, this pages thread)
I would hide the add a chat button for a second or animate it to giveth user feedback. This chat should now show in the thread list of chats
but i cannot put 2 lists togheter i am not working in bubble.io i want to keep it in native mobile so it has to be 2 pages or do i have to put the whole structure in one page? i dont even know how 
You can put two lists together you would need two short list elements
but it will not clipping? like the shortlist for chatmessages i used before did cut off the chats
If you put a container around it the container should grow as the list grows. In bubble the containers are called groups
so i have to create one list for creating new chat messages and one list for the threads who already exist if im correct what you were saying?
So if you look at the way chat TPT is set up the columns on the left have a list of projects which are your threads and then a nested list of chats that are part of this project and then below all of that it has a list of chats that have no project. So you would want to set up two main short lists. One for the list of threads then one for the list of chats that don’t have a thread. Then you can even go deeper where if the user clicks on the thread it shows you a short list of chats do that you would put a short list inside of thread shortlist. It starts to get complicated and hard to explain without showing somebody so basically you would create a custom state on the page that is a thread when you click that thread and make the custom State the current thread which would then show the list of chats for that thread. I would limit the short list for these chats within the thread to maybe five of the most recent chats and then have a group that appears at the bottom of that list of chats that says either show more or just an indicator that there are more maybe three dots
i Understand what you mean but I don’t what a shortlist like a chatlist because it cuts off i want the other page for the chats it is still for mobile so i dont want it too complicated for the customer experience so what would you suggest to keep it this page and send them to another page i am open for a different layout but i dont want everything on the same page. (happy new year by the way 
)
The short list only cuts off because you dont have the parent groups setup to grow with content
I would make 3 separate pages then, one for list of threads, one for list of chats, and one for the actual chat
This issue happens because the Chat page is loading messages using a “current chat/thread” context that is only set when you click an existing chat from the list. When you create a new chat and immediately navigate to the Chat page, that context is still empty, so the repeating group search becomes something like “Messages where chat = empty,” which returns no results. The chat exists in the database, but the page doesn’t know which chat to display until you go back and click it again.
The correct fix is to always send the exact thing your messages repeating group is searching for when navigating to the Chat page. The most stable approach is to use a single Conversation (or Chat) data type and link Messages directly to it. Set the Chat page “Type of content” to Conversation, and when the user clicks “New Chat,” first create a Conversation and then navigate to the Chat page with “Data to send = Result of step 1 (Conversation).” Your messages repeating group should search for Messages where conversation = Current Page’s Conversation.
If you keep Threads, don’t mix contexts. Either load messages by Thread or by Conversation, not both. In that case, create a Conversation inside the Thread and send that Conversation to the Chat page. Once the page always receives a valid Conversation/Chat, new chats will load immediately without needing to go back and click them again.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.