Hi, is there any way I can get a complete listing of the window code? The functions, procedures, click events, etc., so I can examine it as a whole?
You can you be more specific please? Do you want the to show the code of the whole Window, or only the Properties, Method signatures etc.?
@Federico_Giannetti did you look into the docs?
I would like to have the code of the entire window so I can understand where the problems lie… the procedures, the functions, the button events…etc.. without having to open every single thing.
what problems?
Are you saying you do not understand what events, properties and methods are of a window?
Mac terminology: You can save the entire project as a Xojo Project using the Save As… menu item under the FileMenu. It will offer creating an empty folder to house all the pieces of the project, and it makes sense to do that. Then you can go to this folder in the Finder and find the window that you want to examine. (say nameOfTheWindow.xojo_window). Then open that file in a text editor and you will be able to see all the code, properties, events etc. associated with that window in a single location.
beautiful, I’ll try it right away.
No, I just want to read the complete code listing for a specific window.
I tried "Save As" and "Export .." but it doesn't work... opening the saved files with an editor makes no sense!! Where am I going wrong?
You will want to save project as Text or XML not Binary
In Xojo IDE Edit → Options → Under General choose Default project format
or menu file/print .. to pdf if you just need a review
1 Like
Select the Window you want to get its code first… then Print to PDF…
1 Like
Ok it’sWORK !!
thanks, work fine !!
When select File→Save As…, a Dialog Window appears. There is a PopUp adjacent to Format: that provides three choices.
- Xojo Binary Project
- Xojo XML Project
- Xojo Project
For this purpose, choose Xojo Project no matter what your default is. I happen to use Xojo Binary Project as my default, but I can override that here. If you have selected Xojo Binary Project, it will produce a file that is not human-readable. If you select Xojo Project, then it will provide what I described in my original post.
The file produced, when examined in a text editor, has more information than the PDF produced by the MarkusR/Emile Schwarz solution and perhaps is easier to copy from.
The MarkusR/Emile Schwarz solution, which I had never stumbled across, is quite elegant if you are just reviewing code.