BUG (Leopard 10.5): push-button looks like square button

brainois · Post by **brainois** » Sat Feb 16, 2008 9:54 am

Hello,

I am facing a bug (maybe already reported): when you increase the height of a push-button (the one with the aqua-style) to 25 px and above, it automtically takes the appearance of a square button. If you go back to a height below 25 px, then it returns to its normal aqua look-and-feel.

I am wondering when we can expect a Leopard compatible version of Revolution. Considering the amount of money you ask for Runtime Revolution, I would expect much more reactivity... Leopard has been released three months ago and we are still waiting for an update.

Regards

FranÃ§ois

Janschenkel · Post by **Janschenkel** » Sun Feb 17, 2008 12:22 pm

Bonjour FranÃ§ois,

Apple has guidelines that dictate which style button should have which size - the same applies to Java applications, where the 'bounds' of a button can result in the same effect.

Jan Schenkel.

brainois · Post by **brainois** » Mon Feb 18, 2008 10:54 am

Thanks for your answer...

BTW, the small incompatibilities with Leopard do not prevent enjoying RunRev.... but it I am still looking forward the official "Leopard Ready" version!

Janschenkel · Post by **Janschenkel** » Mon Mar 03, 2008 1:10 pm

FranÃ§ois,

Have you reported this problem in the Quality Center? http://quality.runrev.com
Doing that will allow the RunRev engineers to confirm it and perhaps modify their code to circumvent this limitation.

Jan Schenkel.

whelkybaby · Post by **whelkybaby** » Mon Mar 03, 2008 2:39 pm

If I remember correctly, it's already been posted there.

If the height of the button exceeds a certain limit, it will be drawn as a rectangle and not a rounded button. This is because Rev draws the buttons using OS X's own routines. In Leopard, the distinction between rectangle and rounded buttons was made but it was not present in Tiger.

Steve

Janschenkel · Post by **Janschenkel** » Thu Mar 06, 2008 6:47 am

Aha, I see it's QC entry #5698 - and it is indeed, as I suggested, an issue induced by changes in the MacOSX drawing routines.
Let's hope this behaviour is documented somewhere as a known limitation, to cut down on the number of surprised reactions from the general public.

Jan Schenkel.