is your project saved as Binary or as Text?
Text
Emile, thanks for suggestions but the problem occurred in original code in Xojo2018, and then after converting the code to newer version in all releases of 2023 and 2024.
Checking the hard disk will not help with that.
Greg, I donāt think the binary vs text should matter, the IDE handles both and should behave the same way regardless.
I can tell you for a fact that saving as binary and saving as text are completely different from one another. When your project is binary, if anything has changed, the entire project file gets saved. With text, the IDE marks individual items as needing to be saved using the undo system (this happens to be a refactor that I personally did in 2021). Using undo has the unique advantage that things that the IDE can be fairly certain that the user made the change and it needs to be written to disk.
So yes, the format of the project is very important here, as well as whether the change is undoable. If the change isnāt undoable, then it needs to be (but thatās not the case here, I checked). If when you move the item it doesnāt dirty the appropriate part of the project (in this case the project manifest) such that when you then hit File > Save the item is modified on disk then itās a bug in the specific undo action for moving items in the project.
Greg, thank you for explaining the difference, I appreciate you taking time to do so.
However, the IDE is supposed to hide the internal complexity of Xojo code from developer and expose only the functionality that allows developer to create apps. In this sense the Xojo is a product (aka tool) used by customer (aka developer) just like the proverbial pen for the writer, good writer can create book with crapy pen but it helps if the pen is functional and looks good, the similar goes for Xojo in my mind. Anything that makes the process of creation Xojo app more efficient, easier and more more satisfying helps developer to focus on the task of providing his/her customer with better product.
So, we are like links in the chain depending on each other. The Web App I work on is used by support people managing biz processes for other people, they donāt care how much I āsufferā with IDE, they expect something to help them do the job.
Anything that makes life easier for any party in the process will ultimately translate in satisfaction and better life for everybody understanding this. Thank you again for your comments.
Thatās a very interesting sentiment⦠but as I donāt work for xojo any more (can you believe itās been almost 3 years?), I donāt subscribe to the sentiment that the internal workings need to be hidden. And hiding the details doesnāt change the fact that they do work this way. Thereās no getting around that except to have the IDE save each and every file in a text project, every time it saves⦠which is what I was trying to stop from happening.
P.S. If you donāt want to read my detailed explanations, I suggest you mute me because Iām probably not going to stop.
P.S. If you donāt want to read my detailed explanations, I suggest you mute me because Iām probably not going to stop.
Where are you getting this idea from? ![]()
I appreciate your comments and experience. Have a great day!
Smile⦠Paul has posted a Workaround for Issue 77630.
This reminded me that Iām using this reorder workaround for ages. Itās become one of the Xojo specific habits one doesnāt even remember (such as always āsave-before-runā) ![]()
Thanks for filing this issue. Now that Xojo has an official issue for that which they can even reliably reproduce, chances are that we get this IDE behavior improved (sooner or later).
Youād need a Pref for it, since pesonally I prefer alpha ordering of items of the same type.
I do prefer a ālet it where Iāve put itā, and some right click reordering commands as (add more types):
Reorder Items -> Local -> Ascending
-> Descending
Local and below -> Ascending
-> Descending
Well, I keep candle and box of matches handy all the time since we loose power (aka electricity) often but that doesnāt stop me from NOT accepting the poor quality of the grid in the area where I live. So, having workaround is good but having true solution is much better!
![]()
I would prefer a setting, which defines if automatic or manual sort mode is active.
If several developers work on a project I donāt want changes due to sorting in the repository.