jv16 PowerTools 2017 Release Candidate 1

jv16

mrtee wrote
And another one (this is already mentioned before). jvPT doesn´t exit completely. It stays on the taskbar below. (You can´t stop it with a rightclick or start it again, the taskmanager is needed to kill it). The problem is that this doesn´t occur everytime, so it depends likely on the last function that is been used.

I can confirm this action, it also shows usage of 25 to 30% of CPU resources. Just opening jv16 RC1 keeps the program in the Quick Launch area and it is necessary to shut it down using task manager. Or is this by design (that it not exit)?

It is a bug. We are working on a fix.

siliconman01

jv16 wrote
siliconman01 wroteThis applies to Windows 10 x64 Insider Build 14393 and jv16 RC1.

In CFMC, when I move the "aggressiveness" slider bar to a new position, the bar and pointer disappear, never to return again.

CFMCAggressiveSliderBar.png

Can anyone else reproduce this issue?

Jouni,

Are you not able to reproduce this issue? It is 100% reproducible on my Surface Pro tablet, on my Dell XPS 8700, and on my ASUS ROG Maximus VIII Extreme home built computer....all operating with Windows 10x64 insider build 14393 (and earlier builds). I have no computers running where it does not exist as a problem.

jv16

siliconman01 wrote

Jouni,

Are you not able to reproduce this issue? It is 100% reproducible on my Surface Pro tablet, on my Dell XPS 8700, and on my ASUS ROG Maximus VIII Extreme home built computer....all operating with Windows 10x64 insider build 14393 (and earlier builds). I have no computers running where it does not exist as a problem.

We are not able to reproduce this issue with any of our test environments (virtual or real). Might be relating to a specific version of Windows 10. We are investigating.

siliconman01

jv16 wrote
siliconman01 wrote

Jouni,

Are you not able to reproduce this issue? It is 100% reproducible on my Surface Pro tablet, on my Dell XPS 8700, and on my ASUS ROG Maximus VIII Extreme home built computer....all operating with Windows 10x64 insider build 14393 (and earlier builds). I have no computers running where it does not exist as a problem.

We are not able to reproduce this issue with any of our test environments (virtual or real). Might be relating to a specific version of Windows 10. We are investigating.

Here is what causes it:

1. Go to Settings>User Interface

2. Change "Less Windows (Modern user interface)" to "More windows (Classic user interface)"

If I change the above setting back to the default "Less Windows....", the slider reappears and works as designed. It does not disappear when moved to the various positions.

SliderBar.png

siliconman01

This applies to Windows 10 x64 insider build 14393 with jv16 RC1

If the taskbar is not located on the bottom of the monitor, jv16 CFMC does not fill the full screen when running a scan. See pic. This has been occurring on previous versions of jv16 and has been reported before.

Full Screen Issue.png

Update: In further testing, this does not appear to be related to the location of the task bar at the bottom of the screen. It is occurring even when the task bar is at the bottom.

jv16

siliconman01 wrote
jv16 wrote
siliconman01 wrote

Jouni,

Are you not able to reproduce this issue? It is 100% reproducible on my Surface Pro tablet, on my Dell XPS 8700, and on my ASUS ROG Maximus VIII Extreme home built computer....all operating with Windows 10x64 insider build 14393 (and earlier builds). I have no computers running where it does not exist as a problem.

We are not able to reproduce this issue with any of our test environments (virtual or real). Might be relating to a specific version of Windows 10. We are investigating.

Here is what causes it:

1. Go to Settings>User Interface

2. Change "Less Windows (Modern user interface)" to "More windows (Classic user interface)"

If I change the above setting back to the default "Less Windows....", the slider reappears and works as designed. It does not disappear when moved to the various positions.

Ah, that makes sense, now I can see why we were not able to reproduce the issue. I made some changes in order to attempt to fix the issue (still cannot reproduce the issue though), and a notice about this was added to the Classic User Interface to the Settings window.

Thank you for reporting!

jv16

The RC2 has been released. Please see: https://www.macecraft.com/forum/viewtopic.php?f=10&t=5819

« Previous Page