2 changes to old version

[oldwexi]

2 issues:
1.) Cant lower vertically the the size of History Explorer!
See Screencopy.

2.)Interesting behavior of new Version.
Load Image
load RangeSelection process
execute RangeSelection which creates rangemask image.
When clicking RangeSelection process top bar or other top bar the rangemask Image windows empties!!
When i click on the rangemask mage top bar the data are back. And so so on....
When the window is empty i can paint in the window....

When loading a project the Windows of the Project dont get empty - only new Images get empty and filled etc...



Have uninstalled reinstalled always the same error.
have reinstalled 1023 Version everything runs nicely!
(Win 7 Prof)

Gerald

[Juan Conejero]

1.) Cant lower vertically the History Explorer!

I can't reproduce this problem on any of our machines (Windows and Linux). The History Explorer window has a minimum height, but you should be able to make it smaller vertically as shown on your screenshot.

When the window is empty i can paint in the window....

Yes, I have seen this screen drawing issue happen occasionally on one of our virtual Windows machines. It is obviously a Qt 5 bug, but it only happens rarely on this machine. I am sorry to know that it happens so severely in your case.

Have you enabled child window transparency? Please check the following:

- EDIT > Global Preferences
- Preferences > Special GUI Effects

Make sure that you have the Translucent workspace child windows option disabled. If you have it enabled, this can be the cause of the problem.

[Harry page]

Hi

I like this one as well

Harry

[Juan Conejero]

Nice screenshots! This bug should be now fixed in version 1.8.4.1170, which I have just released.

[oldwexi]

Hi Juan!
Thanks for the new PI Version and thanks for the fast improvement of the .1169 Release version.
The new images in  the windows are stable now!

The vertical resizing issue of the HistoryExplorer is still there in both of my installations.
I am using two 1920x1200 Pixel Screens side by side on the main pc and
i am using also a notebook with 1920x1080 resolution.
(the vertical sizing issue happens also with ProcessContainers.)

Could it be that i have to set something in the GUI Profile ?
Any hint would be helpful as i searched and tried but did not find anything so far.

Gerald

[Juan Conejero]

Hi Gerald,

The HistoryExplorer and ProcessContainer windows have minimum heights of 400 pixels (speaking of logical pixels, which get scaled automatically on high-dpi screens). I think these minimum dimensions are quite reasonable, but I can lower them a bit in the next version.

1920x1200 is really a borderline resolution for PixInsight, and 1920x1080 is clearly too low. I strongly recommend working with higher resolutions. 27" 4K monitors are very accessible now, and they work fantastically for PI 1.8.4. For example, I am now using a Dell P2715Q monitor on one of our workstations.

[georg.viehoever]

Hi Juan,

please consider that some of us are using laptops while in the field. Therefore, IMHO, PI should continue to work on a moderate resolution laptop as well. (After all, we want to invest our money into PI licenses and telescopes, not in laptops...  )

Georg

[Juan Conejero]

Yesterday I was testing 1.8.4.1170 on a 1920x1080 laptop with Windows 8.1, and it worked very well (considering that it was Windows, after all...  ). Much more than sufficient for a field use IMO. So I think we don't have such problem at present.

However, for serious image analysis and processing work, 1920x1200 is borderline in the sense that it can be considered barely the minimum required resolution to work comfortably. 1920x1080 is way below that limit, IMO.

[oldwexi]

Juan!
Thanks for the explanations.
Gerald

[msmythers]

Juan

What has changed in the PI workspace or architecture that would make 1920x1080 not comfortable? While I'm not a professional and PI is more aimed towards professionals the thought of making a software package hardware requirements based on hardware that is not used by a majority yet seems wrong. To me if there was a reason one could not process an image in a 1920x1080 environment then so be it. It's almost like saying that the new requirement will be 32gb of ram because anything less makes processing times to long. It is all relative to the user I think? If it causing to many complaints then I understand. I do think it would be interesting to know how many users are using what resolution monitors.   

I fully enjoy PI. I use it for all of my imaging, daytime and nighttime. I use it for processing images from my tablet. I tell people and show people what PI can do so I hate to think one day I will have to spend a lot(for me) of money on a monitor and video card just to continue to use the latest version. I do know that someday I will have to get new hardware but I hope it is not because of software.

Please don't take this personally. When I was working I worked directly with programmers to help develop wonderful and amazing code. I have all the respect for what you have to do and as a past business owner I understand that the business side must grow also and that will mean change.

Thanks to you and all those involved for all the extremely hard work. I do appreciate it.


Mike

[lucchett]

Juan, I think that PI must not look great on low res monitor, but I hope the platform will remain "usable" with low res.

I personally run preprocessing remotely through an RDP connection, and due to the bandwidth I prefere to have small resolution and color depth.
I only transfer the master frames at the end of the pre-processing.

So far I had to manage a very crowded desktop, not easy but possible and that was enough.

A lot of friends with remote observatories work in the same way, because wiMax symmetric lines are very expensive.

I hope this is compatible with the Pi evolution.

ciao,
Andrea

Thanks,
Andrea

[llpastro]

I have a 22" monitor running at 1680 x 1050 and I am happy with it.  Perhaps my expectations are low but I feel I can get everything I want out of my images.  I can sit close to monitor.  Perhaps that helps.

Larry

[tommy_nawratil]

hi,

muchas gracias por su actualizacion 

nice to see Gerald starting to paint in Pixinsight 

my bug on 1.8.4.1171:
preprocessing script finishes like normal. But when trying to open the newmaster light,
Pix Insight freezes and must be killed by task manager. Reproducable.
Thisis on my dedicated PI workstation Win7/64

Also with the new install all scripts that I have loaded mus be re-loaded.
And I too do not like the new font too much, but I can read it.

btw - could I possibly have version 1.7 for Win32 in the download area? I still have one workstation on XP/32 for everyday work.
So i work every day on it, and analysing pics is part of my work 
Supported or not, this version worked while 1.8 does not:
Cannot open more than one DSLR pic there, get "MAD cannot be calculated" error. Makes me MAD and SAD 

saludos cordiales amigos!
Tommy

[Juan Conejero]

preprocessing script finishes like normal. But when trying to open the newmaster light,
Pix Insight freezes and must be killed by task manager. Reproducable.
Thisis on my dedicated PI workstation Win7/64

I can't reproduce this behavior on Windows 7 and Windows 8.1 with any of our test data sets. Can you upload the master light image in question, along with an icon (xpsm format) of the BPP instance used?

Also with the new install all scripts that I have loaded mus be re-loaded.

If you refer to unofficial scripts, the new version requires reinstalling them manually as a result of important changes in application settings. This is not a bug.

And I too do not like the new font too much, but I can read it.

You can change the font very easily:

- EDIT > Global Preferences
- Preferences > Core UI Resources
- Set the desired font name in the low-resolution font or high-resolution font, as appropriate.
- Click Apply Global or press F6
- Exit PixInsight
- Launch PixInsight.

[Juan Conejero]

btw - could I possibly have version 1.7 for Win32 in the download area? I still have one workstation on XP/32 for everyday work.

Sorry, no. In fact, the current 32-bit 1.8 version for Windows will be removed in September. This obsolete 32-bit version is generating problems and misinterpretations that we really don't need.