realbasic-nug
[Top] [All Lists]

Re: Colors Window Problem

To: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Subject: Re: Colors Window Problem
From: Paul Young <youngpr@myactv.net>
Date: Thu, 30 Oct 2008 12:41:27 -0400
Authentication-results: mx.google.com; spf=neutral (google.com: 74.124.194.228 is neither permitted nor denied by best guess record for domain of realbasic-nug-bounces@lists.realsoftware.com) smtp.mail=realbasic-nug-bounces@lists.realsoftware.com
Delivered-to: listarchive@realsoftware.com
In-reply-to: <661E08E4-F1F9-4364-91BB-948CA50C1F4D@stretchedout.com>
References: <2EE8BB71-8795-4B8E-BA48-C10A68465126@myactv.net> <661E08E4-F1F9-4364-91BB-948CA50C1F4D@stretchedout.com>
Reply-to: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Sender: realbasic-nug-bounces@lists.realsoftware.com
Greg,

Sorry, that was a typo.  The RB meant was 2007 Rel 5.

Good idea to put the code in the MouseUp.

I am seeing this problem in four of my apps which use the Color Wheel.


On Oct 30, 2008, at 12:26 PM, Greg O'Lone wrote:

On Oct 30, 2008, at 12:04 pm, Paul Young wrote:

Last night I realized that I had a problem accessing the Apple Colors Window.

I was able to reduce the problem to a very simple project as follows:

a. Make a new project. Drag a rectangle into Window1 and put this code in MouseDown:

                Dim b as Boolean
                Dim c as Color

                b=SelectColor(c, "Select a Color")
                Rectangle1.FillColor = c

                Return True

b. When I run the project and click on Rectangle1, the Colors Window comes up. I select a color and click on the "OK" button.

c. Rectangle1 is filled with the selected color. Everything normal so far!

d. If I click again on Rectangle1, the application hangs. I must Force Quit this project.

I am running OS 10.5.5 on a MacBook Pro using RB 2008 Rel 4.1 OR RB 2008 Rel 5. Does anybody see a problem here?

Paul,

I too am using 10.5.5, MacBook Pro but using 2008r4.2 (didn't know there was an 08r5 already), but I am not seeing the crash. I copied your code directly.

I would suggest that you return true in the MouseDown event and then execute the rest of the code in the MouseUp event though. It'll be more consistent with buttons that way (it would allow a user to click and then "oops I didn't want to do that so I'll drag my mouse off the button first" kind of action.)
Greg

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>