problem positronstudio

[krizpin]

Good afternoon. I'm having several problems with the software. In addition to this address error, it does not let me save the files with another name either. file-- save as... doesn't work
thanks

[John Drew]

Hello Krizpin,
Two things to help you get started.
Firstly please change the name of your post so that people know it's about saving or some other issue.
Secondly without knowing about the code we can't help.

Because it's in the test section I'm not sure if it's really a test or a call for help.

John

[JohnB]

@krizpin Please try this version.  Its just the 64bit executable file so save the original and replace it with the file in the link.
Please in future post questions on Positron Studio on the appropriate thread

[krizpin]

ok thank you all for your help. I'm going to try it right now.I'm sorry I hadn't noticed the thread about positron

[ArifCan]

Good Morning,
I downloaded and installed the latest version 2.0.3.14 of Positron Studio 2.
I did it without remowing/deleting the installation 2.0.2.9 which was working without problems at saving.

I am also having the problem of krizpin: The "save as" window does not appear. I recognized that the code can be compiled but the .bas is not saved. My OS is Windows 11.

Then I uninstalled the Positron Studio 2.0.3.14 and made a fresh install. The same problem: When save as is clicked, no window opens. Nothing happens. So, I had to re-install 2.0.2.9 because I could not find any of the recent versions (other than the latest:2.0.3 Build 14) to try out.
I would be glad to receive your suggestions.

[JohnB]

Please try this new version.  It's a full install of a beta version 15.  Let me know how you get on.

[ArifCan]

Dear John, I installed the Beta version 15.
Description of what what I do:
- I open one of my .bas files.
- I change a single character in one of the HRSout lines.
- I click on the "Compile file" button.
Normally, the file will be saved and Positron Studio will call the compiler to make a compilation of the code. This is not happening.
Here the result:
The file is saved as .bas (when I re-open I see the change I made). Positron studio finishes its job quite quick and does not do anything further.
The file is not compiled. When I check, I see that I still have the old .hex file in my folder.
When I try to close the .bas file, a window opens and asks if I want to save it.
When clicking "No" (because I know it was already saved when clicking "compile") another pop-up message appears:
"Access violation at address 0000000000409E05 in module 'PositronStudio.exe'. read of address 00000000000008A8."

[ArifCan]

Forgot to tell: in version 15 the "save as" is working. The expected window is popping up.

[JohnB]

Using version 15, I have just tried something similar with one of my programs but I could not repeat the problem.
Are you just using a single source file, do you reference include files in your source, are you using Program Manager, Does this happen on all your .bas files?
If its only on specific files can you share the file with me.

[ArifCan]

It is a small program where I make use of the TFT library of Atomix. So yes, it has include files.
I checked also other .bas files. The error is happening on all. So far I have not built projects. I open single .bas files.
Also the "access violation" message appears when closing the .bas without saving it.
Another Test: 
I opened the sample program Ser_Buffer and made a change in the wording "Buffer Overrun" (for example as "Buffer ovrrun").
When I first save the file(it is saved-no problem here) - then close it - and then open it again and then click compile, it compiles.
But when I make another change on the open program and directly click compile, the Studio only saves the bas. but does not compile the file.
(I could not answer your question about Program Manager, sorry, I did not understand what you meant).

[JohnB]

You will have to leave it with me while I try to replicate it.  I'll get back to you when I have a solution.
I the meantime I suggest you revert to the earlier version which worked for you or bavk to the original IDE.