Very Minor 1.8.4 Issues

[Warhen]

Excited to see project compression- the last line of that mouseover hint is chopped off.

When clicking cursor in certain fields (PixelMath expressions), I can't see the cursor position (vertical line) initially.

So far, that is all I have found- bravo!

[jkmorse]

If I can add one more small item, it seems the "abort" button on the process console is missing.  I can still abort by closing the tool but not sure the deletion of the abort button was intentional.

Best,

Jim

[Carlos Milovic]

Jim, this is odd... I have the abort button (running Fedora right now, but I'll check later in Win8).

[jkmorse]

It is a Win 8.1 machine.  Not critical, just a nice to have.

Thanks,

Jim

[jkmorse]

Carlos,

This type of thing is making me, once again, seriously consider a dedicated Fedora machine (with upgraded resolution to beat my current 1920 x 1080).  Your system is always so much more stable than Windows.

Best,

Jim

[Warhen]

I'm not hearing any warning tones as before.

[Juan Conejero]

Jim, that should not happen. Do the following to "force" the Process Console window to have the correct dimensions:

- On the Process Console window, click the "Placement" button (blue down arrow, top right corner).
- Select a location at the right side. For example, "Right Top"
- Now you can resize the window by dragging its left edge. The Abort button will be shown
- Placement button again and "Left Top" to send the window to its normal position.

Let me know if this helps.

[Juan Conejero]

Your system is always so much more stable than Windows

Besides different opinions about operating systems (I don't want to start an OS war here!), the Linux version is the reference implementation of PixInsight. In the foreseeable future, it will always be the most thoroughly tested, stable, feature-rich and evolved version.

[Juan Conejero]

Hi Warren,

Glad to know 1.8.4 is working well for you. Yes, project compression is a big step forward. I am sure most users will love this feature as they discover it.

I still have to write a number of posts and tutorials to describe a lot of things, including project compression, the new XISF features, the new preferences options to control UI scaling, and a large amount of information for developers. I'll start to write them once I manage to get some rest. I am in Galicia right now, so you know, good wine and food, green forests and cows everywhere... just what I need to recharge batteries

the last line of that mouseover hint is chopped off.

Yes, this happens with tool tips shown for combo boxes. It happens also in previous versions of PixInsight, at least since version 1.4. Always hover the text label to the left of a combo box, where the same tool tip is usually shown without problems.

This is a Qt bug that we have been suffering since at least Qt 4.1 or 4.2, and it still happens in Qt 5.5. We are talking of 8 or 9 years...

The only practical solution to this problem, which makes me sick, seems to be that I write new code from scratch to replace Qt's tool tips, at least most of them. I'll try to face this task for the next version.

When clicking cursor in certain fields (PixelMath expressions), I can't see the cursor position (vertical line) initially.

Yes, this happens. This looks also like a Qt 5 bug, since it never happened with Qt 4. Or perhaps I am doing something wrong at a very low level. I'll have to investigate.

[jkmorse]

Thanks Juan, I will give that a try (and only whisper about my loathing of Windows  )

Jim

[Warhen]

Juan, I'm hoping you have someone better looking than the cows to share the wine with. ;>) Sounds nice though- we are fortunate enough to be surrounded by a few hundred acres of the neighbor's grazing land. 

See attached graphics.

[llpastro]

I have the same behavior.  Was not a problem in previous version.  Win 7 64 bit.

Larry

[jkmorse]

Carlos & Juan,

Based on the recent updates, especially the recommendations re minimum resolution, I am building a new PI processing system and am once again going to try Linux, this time Fedora 22.  My question goes to setting up swap partitions for PI.  I know I can set up a swap partition on each physical drive (I am putting in 2 250GB SSDs as well as a large HDD for basic storage) and I have read that I should make the swap partition the same size as my RAM (32Gb).  I intend to put my swap partitions on the two SSDs. Now my questions:

1.  For PI, would 32Gb swap partitions be the right size or should I use some other size?

2.  Should I create more than one swap partition on each SSD?

3.  If so, I cannot find out how to create multiple swap partitions on the same physical drive, recommendations? (is it as easy as labeling them "swap1", "swap2"?)

4.  In either case, can I point to the same swap partition multiple times and still get a performance boost in PI? If so, are their limits to how many times I should point to the same swap partition?

Sorry for the basic questions but trying to make sure I do this right and you guys should know.

Thanks,

Jim

[Alejandro Tombolini]

Hi Jim, I don't know too much on this but may be can help.

1) I use a 240 GB ssd Disk with 32 GB swap partition
2) I think it is not necessary.
4) Now you can point the same partition multiples times. See this video. My best benchmark are with ram disk. I use it as shown in the image.
See also here.

Saludos,
Alejandro.

[jkmorse]

Alejandro,

Thanks for that.  Now I just need to figure out how to do ram disks in Linux 

I will be starting the Linux adventure next week and will report out how it goes.

Best,

Jim