On my MacBook Pro version 3.1, running Mac OS 10.6.8, I found that when adjusting the temperatures for Custom settings by using the little arrow controls to the right of the entry box, the increment or decrement seems to "stick" and the value will continue to increase and decrease all the way to the available limit.
Not a huge deal as directly entering a value works, and of course the settings don't take effect until clicking on "Okay", but in previous versions the arrows worked as I've always expected them to, by changing one value per mouse click and not running away like this.
Macs Fan Control 1.2.1
MacBookPro3,1
Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz[100]
Mac OS X 10.6
Fans:
Left side-min{2000}curr{2002}max{6000}mode{2,TC0D,84,94}
Right side-min{2000}curr{1999}max{6000}mode{2,TG0D,76,86}
TempSensors:
TB0T (Battery TS_MAX) - 30, 30
TC0D (CPU Diode) - 63.875, 63.875
TC0P (CPU Proximity) - 55.375, 55.375
TG0D (GPU Diode) - 67, 67
TG0H (GPU Heatsink) - 55.875, 55.875
TG0V () - 60.0273, 60.0273
TGTV () - 127, 127
TTF0 () - 70, 70
TW0P (Airport Card) - 34.5, 34.5
Th0H () - 54.75, 54.75
Th1H () - 40, 40
Th2H () - 42.375, 42.375
Tm0P (Mem Controller) - 45.5, 45.5
Ts0P (Left Palm Rest) - 32, 32
Disk drives:
HGST HTS721010A9E630 - 32
We have discontinued this forum and moved support tickets to the GitHub issue tracker. More info
Possible bug in 1.2.1
Moderator: Steven
Possible bug in 1.2.1
Frank Lockwood
MacBook Pro 3.1, 2.4 GHz. Core2Duo
Mac OS 10.6.8 - MFC version 1.2.1
Windows 7 SP1 32 bit Pro via Bootcamp 4.0.4033
Mac Mini 6.2, 2.3 GHz. i7
Mac OS 10.8.5
Windows 7 SP1 64 bit Pro via Bootcamp 5.1.5621
MacBook Pro 3.1, 2.4 GHz. Core2Duo
Mac OS 10.6.8 - MFC version 1.2.1
Windows 7 SP1 32 bit Pro via Bootcamp 4.0.4033
Mac Mini 6.2, 2.3 GHz. i7
Mac OS 10.8.5
Windows 7 SP1 64 bit Pro via Bootcamp 5.1.5621
- Steven
- CrystalIDEA Developer
- Posts: 2294
- Joined: 21 Dec 2009, 11:48
- Location: CrystalIDEA headquarters
- Contact:
Re: Possible bug in 1.2.1
can you please give me an exact example (with exact values, parameters, maybe with a screen) of such situation?On my MacBook Pro version 3.1, running Mac OS 10.6.8, I found that when adjusting the temperatures for Custom settings by using the little arrow controls to the right of the entry box, the increment or decrement seems to "stick" and the value will continue to increase and decrease all the way to the available limit.
Re: Possible bug in 1.2.1
I've found the same behaviour on my white-face iMac, version 6.1, also running OS 10.6.8.
Here is a link to a screen capture movie:
https://www.dropbox.com/s/oke422r06we6y ... y.mov?dl=0
Note that in each instance, I'm not clicking multiple times, or clicking and holding - I'm just clicking once.
Here is a link to a screen capture movie:
https://www.dropbox.com/s/oke422r06we6y ... y.mov?dl=0
Note that in each instance, I'm not clicking multiple times, or clicking and holding - I'm just clicking once.
Frank Lockwood
MacBook Pro 3.1, 2.4 GHz. Core2Duo
Mac OS 10.6.8 - MFC version 1.2.1
Windows 7 SP1 32 bit Pro via Bootcamp 4.0.4033
Mac Mini 6.2, 2.3 GHz. i7
Mac OS 10.8.5
Windows 7 SP1 64 bit Pro via Bootcamp 5.1.5621
MacBook Pro 3.1, 2.4 GHz. Core2Duo
Mac OS 10.6.8 - MFC version 1.2.1
Windows 7 SP1 32 bit Pro via Bootcamp 4.0.4033
Mac Mini 6.2, 2.3 GHz. i7
Mac OS 10.8.5
Windows 7 SP1 64 bit Pro via Bootcamp 5.1.5621
- Steven
- CrystalIDEA Developer
- Posts: 2294
- Joined: 21 Dec 2009, 11:48
- Location: CrystalIDEA headquarters
- Contact:
Re: Possible bug in 1.2.1
fbl
I'm sorry maybe I don't understand - didn't notice anything unusual. Also you pressed 'Cancel' every time and I'm not able to see if setting custom values really works.
I'm sorry maybe I don't understand - didn't notice anything unusual. Also you pressed 'Cancel' every time and I'm not able to see if setting custom values really works.
Re: Possible bug in 1.2.1
When set, the Custom Setting works as it should - that's not what I'm asking about.Steven wrote: didn't notice anything unusual.
What I am inquiring about - and it's not a huge deal, but rather an annoyance - is how a single click initiates the values running away, rather than simply incrementing by one and leaving it at that. To reiterate, in my video, I only clicked a single time on the up or down arrow, with the unexpected result that the values take off in the indicated direction. In any other program I've used on a Mac, including earlier versions of MacsFanControl, I've never seen this behaviour, hence my inquiry as to whether it's a bug.
..., guess it's a feature.
Frank Lockwood
MacBook Pro 3.1, 2.4 GHz. Core2Duo
Mac OS 10.6.8 - MFC version 1.2.1
Windows 7 SP1 32 bit Pro via Bootcamp 4.0.4033
Mac Mini 6.2, 2.3 GHz. i7
Mac OS 10.8.5
Windows 7 SP1 64 bit Pro via Bootcamp 5.1.5621
MacBook Pro 3.1, 2.4 GHz. Core2Duo
Mac OS 10.6.8 - MFC version 1.2.1
Windows 7 SP1 32 bit Pro via Bootcamp 4.0.4033
Mac Mini 6.2, 2.3 GHz. i7
Mac OS 10.8.5
Windows 7 SP1 64 bit Pro via Bootcamp 5.1.5621
- Steven
- CrystalIDEA Developer
- Posts: 2294
- Joined: 21 Dec 2009, 11:48
- Location: CrystalIDEA headquarters
- Contact:
Re: Possible bug in 1.2.1
fbl
I got it finally! We use Qt framework for UI, which is cross-platform, and single click + hold= initiates values runaway for most of the platforms (Windows/Linux), that's why it might look a bit weird on Mac.
I got it finally! We use Qt framework for UI, which is cross-platform, and single click + hold= initiates values runaway for most of the platforms (Windows/Linux), that's why it might look a bit weird on Mac.