CPU: 1.25 GHz PPC G4
RAM: 512 MB
GFX: ATI Radeon 9200
OS: OS X 10.4.8
Blender: blender-2.44-RC2-OSX-10.3-py2.3-powerpc.zip
This concerns the number buttons with the small arrows on both sides of the number: when I LMB-hold-and-drag on one of those buttons the value doesn't change at all.
Description
Event Timeline
Logged In: YES
user_id=103
I loaded this test build to verify, but it goes fine.
There was a bug related to this, but that was fixed long ago. You sure it is in the file you loaded?
Angemeldet: JA
user_id=5561
I am quite sure about it. The header says "blender.org 243.2". I checked it against 2.43 and I don't remember that I had this problem before. BTW: I checked again without my personal .B.blend, just blender running, no blend file loaded.
Is there anything else I can do to help?
Logged In: YES
user_id=103
Maybe there is an opengl redraw glitch? After you release the mouse, you can invoke a redraw with Middlemouse click-drag.
Check if the 2.43 release is OK (get it from blender.org).
Angemeldet: JA
user_id=5561
I checked already against 2.43 release as I wrote. If it wouldn't be a new problem which wasn't there with older releases I would not post.
Angemeldet: JA
user_id=5561
To be exact: the value does always change only one unit (1, .1, .01 depending of the actual number button) and always AFTER releasing the LMB.
Example: in Display Buttons (F10) I want to increase SizeX of the Format. I LMB-drag-to-the-right. While dragging nothing happens. After releasing LMB SizeX changes from 640 to 641.
Logged In: YES
user_id=103
The problem is that nobody can redo this now. I use Blender on mac g5 (10.3 and 10.5) without problem.
There was also not any commit I know in the UI that could cause this. So... for the time being the problem is only in your computer, that's why it is important to double check everything.
Maybe you have a tablet connected?
Logged In: YES
user_id=103
You wrote:
"Example: in Display Buttons (F10) I want to increase SizeX of the Format. I LMB-drag-to-the-right. While dragging nothing happens. After releasing LMB SizeX changes from 640 to 641."
That indicates you have your own .B.blend saved. Compare it with 'factory defaults', which is now an option in File menu. This option doesn't save over your personal settings btw.
Further the ball is still in your court. You are the only person with this error, so you can help us by testing more. You sure this ever worked in that system? Try older versions of blender (like 2.32). Can you try it on another computer?
Logged In: YES
user_id=134
Just for completeness, the numbut dragging works in current CVS, Windows Vista.
Logged In: YES
user_id=177
This is strange, this problem should have been fixed a while ago, and it's working fine for me, on a g4 powerbook of similar specs (except the graphics card)..
Can you give some very detailed information on your system please? Have you ever installed any tablet drivers?
Angemeldet: JA
user_id=5561
(Sorry for delay, notification mail was in spam folder.)
1) This feature did work as long as I remember using blender on all platforms. I checked this on my PPC with 2.43, 2.42a, 2.36 with and without my personal .B.blend. I try to check it on one or two other macs the next days.
2) I have no tablet installed and never had one :-(
3) My graphics card spec (it never changed in the past; other info at top of thread):
ATI Radeon 9200:
Chipsatz-Modell: ATY,RV280
Typ: Monitor
Bus: AGP
VRAM (gesamt): 32 MB
Hersteller: ATI (0x1002)
Geräte-ID: 0x5962
Versions-ID: 0x0001
ROM-Version: 113-xxxxx-116
Monitore:
PHL 23PF9946:
Auflösung: 1024 x 768 @ 60 Hz
Farbtiefe: 32-Bit Farbe
Core Image: Nicht unterstützt
Hauptmonitor: Ja
Synchronisierung: Aus
Eingeschaltet: Ja
Quartz Extreme: Unterstützt
Rotation: Unterstützt
4) Please read ALL I wrote in this thread before posting.
5) I know I am the only one with this problem, but I can't help it :-}
Angemeldet: JA
user_id=5561
It all the same with 2.44. I try on two or three other macs and report.
Angemeldet: JA
user_id=5561
GL info from my Mac Mini from GLinfo.blend with 2.44:
Compiled with Python version 2.3.5.
Checking for installed Python... got it!
Detected GL_ARB_texture_env_combine
Detected GL_ARB_texture_cube_map
Enabled GL_ARB_multitexture
Enabled GL_ARB_shader_objects
Enabled GL_ARB_vertex_shader
Enabled GL_ARB_vertex_program
Detected GL_EXT_separate_specular_color
GL_VERSION: 1.3 (1.3 ATI-1.4.18)
Supported Extensions...
GL_ARB_shader_objects supported? yes.
GL_ARB_vertex_shader supported? yes.
----------Details----------
Max uniform components.512
Max varying floats.32
Max vertex texture units.0
Max combined texture units.16
GL_ARB_fragment_shader supported? no.
GL_ARB_texture_cube_map supported? yes.
----------Details----------
Max cubemap size.2048
GL_ARB_multitexture supported? yes.
----------Details----------
Max texture units available. 6
GL_ARB_texture_env_combine supported? yes.
OOh... a mac mini? That gfx card is really not very powerful.
The symptom is that frontbuffer flushing (opengl) is not well supported for every situation. This is one of them... same as for Intel macs.
Because of this we want to make 2.50 completely frontbuffer-drawing free.
(to opengl tracker)
Update: same system as before (except now OS X 10.4.11):
2.43: no problem (!)
2.44: same problem
2.45: no problem
2.46: same problem
Maybe it is something with odd and even release numbers ...
Albrecht: there is probably another variable involved with error then. The frontbuffer updating in Blender hasn't changed in past years.
This is a generic request to test your bug report and see if it is still an issue in 2.5alpha2 if so please let me know by making a comment in this report ie 'also in 2.5alpha2' and I will add it to the 2.5 bug list.