Bug in 'Load' TAB
 
Share:
Notifications
Clear all

15th Feb 2024: Astro Pixel Processor 2.0.0-beta29 released - macOS native File Chooser, macOS CMD-Q fixed, read-only Fits on network fixed and other bug fixes

7th December 2023:  added payment option Alipay to purchase Astro Pixel Processor from China, Hong Kong, Macau, Taiwan, Korea, Japan and other countries where Alipay is used.

 

Bug in 'Load' TAB

5 Posts
2 Users
0 Likes
2,485 Views
(@gnomus)
Red Giant
Joined: 7 years ago
Posts: 46
Topic starter  

I was creating some calibration masters earlier today when I discovered a bug that is reproducible.  I loaded a set of files and produced a series of calibration masters with one type of flat.  I then decided to create a different filter master flat.  I pressed the 'Clear' button.  I then tried to load the new flat frames.  At this point, the APP window 'Gathering frame details' appeared, but it got stuck at 'Completed 1%'.

It did this every time I used it.  Version 1.054 did not do this to my recollection.  It was a bit of a nuisance, since I had to shutdown and startup APP to produce each new Master Flat frame.

Any ideas?


   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 7 years ago
Posts: 4366
 

Hi Steve,

Thank you for sharing, I wasn't aware of this. I'll try to duplicate it and fix it.

You can trigger this problem each time?

Mabula


   
ReplyQuote
(@gnomus)
Red Giant
Joined: 7 years ago
Posts: 46
Topic starter  

Yes.  It does it 100% of the time (for me anyway).


   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 7 years ago
Posts: 4366
 

Thank Steve,

Going to fix it 😉

Mabula


   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 7 years ago
Posts: 4366
 

Hi Steve,

I have just tried, can't seem to trigger the error here yet.

Does it also happen with only 5 frames for instance? Maybe it has to do with the amount of frames in the file list.

The , " but it got stuck at 'Completed 1%" does indicate where the problem is.

It would help as well if you can post the console output when the problem occurs.

The frame list panel is updated after calibration, and for some reason a boolean value isn't switched and the new frame list updater is waiting for an old one to finish it seems.

Update: yes, this is synchronization issue, think I have found the problem..

Mabula

 


   
ReplyQuote
Share: