[quote:8uwg70hp]

Try it for yourself. If you go over a control, and hold LMB, Mouse Button Down will not register it. It literally can not see that in fact the mouse button is being held down.

At least, that is what I am seeing here.

Are you able to verify this?

What do you mean "mouse over a control"?

Can you upload a capx of this?

This means, put the mouse pointer directly over a control, as if you plan to use it. Just like when you click your "submit" button to post a message... you have always moused over the "Submit" button with your pointer, yes? The press your left mouse button.

>

> > You can try either putting an "every tick" "sliderobject.y = 100" while dragging.

> > Which will make the object stay in place.

> > And if it reaches beyond the slider itself you use the x value to keep it at the end.

> > "if sliderobject.x = more than 10" "make sliderobejct.x = 10"

> > "if sliderobject.x = less than 0" "make sliderobject.x = 0"

> > This will keep the sliderobject.x in between 0 and 10 while you're dragging and always on 100y.

> >

> > I hope this made sense and it helps you understand how it might work.

> >

>

> Well, not really... but I am trying.

>

> This code seems to be all about moving the slider *object* (as opposed to the slider handle) around.

>

> I have no interest in moving the slider object anywhere, so I am not sure how any of this helps.

>

> Now, on the other hand, I DO want to move the slider handle left and right... as designed. And it does that... so no biggie.

>

> But nowhere in this discussion do I see how to detect that the LMB is down.

>

> How does the above suggestion tell me that the LMB is down?

>

After you've added the mouse object to your project on the layout, just like you would add a new sprite, you go to your events.

And input this condition: "Mouse > Mouse button is down > Left"

Yes, and I've done that from the very start. What I reported with the OP, is that this the Mouse Button is Down fails to function properly, when the pointer is over a control.

Try it for yourself. If you go over a control, and hold LMB, Mouse Button Down will not register it. It literally can not see that in fact the mouse button is being held down.

At least, that is what I am seeing here.

Are you able to verify this?

You can try either putting an "every tick" "sliderobject.y = 100" while dragging.

Which will make the object stay in place.

And if it reaches beyond the slider itself you use the x value to keep it at the end.

"if sliderobject.x = more than 10" "make sliderobejct.x = 10"

"if sliderobject.x = less than 0" "make sliderobject.x = 0"

This will keep the sliderobject.x in between 0 and 10 while you're dragging and always on 100y.

I hope this made sense and it helps you understand how it might work.

Well, not really... but I am trying.

This code seems to be all about moving the slider *object* (as opposed to the slider handle) around.

I have no interest in moving the slider object anywhere, so I am not sure how any of this helps.

Now, on the other hand, I DO want to move the slider handle left and right... as designed. And it does that... so no biggie.

But nowhere in this discussion do I see how to detect that the LMB is down.

How does the above suggestion tell me that the LMB is down?

> if we filter out the negative ones, then that's really just the definition of bias.

>

And yet you want to filter out negative comments relating to the OP?

The idea is not to protect comments... merely because they are comments. The idea is to protect all *C2 Related* comments, in C2 discussion areas. There should be a free flow of info and opinions about *C2*.

I would think that yes, it would be best for people to voluntarily filter out all messages dedicated to, for example "Miley Cyrus" in C2 forums. Maintaining a bias free environment for Miley Cyrus postings is pointless.

There should be a strong discrimination in favor of *C2* discussion. Therefore calls for the elimination of C2 discussion are uniquely ill suited for posting here... being philosophically contrary to the purpose of the forum.

Back to your regularly scheduled program.

You can use a drag and drop behavior on the slider object and limiting it's movement to only the slider.

I'm very sorry, but I don't understand at all. I see the DragDrop behavior... but I don't see how to relate that to your suggestion. Could you be more specific?

Thank you for your kind help

R

Hi all,

I've discovered that the check for a mouse button down condition... fails if the pointer is over an object.

Example... if the mouse is down whilst on a slider. I had a great solution to a problem... until I found this issue.

Does anyone know a way to detect if the mouse button is down, whilst on a slider (or button, or whatever).... OR... is it possible to do a test on the slider... to see if the control is currently being used? Either should work.

Thanks!

R

Actually, I think that this is a very good/important post. Some people see it as complaining... but it's actually an open criticism, like a product review... we see those on Amazon every day, and it really helps people make informed decisions. Wronghands gave me something to think about, as I look into the possibility of purchasing a License.

Accurate and fair assessments should always be encouraged... if we filter out the negative ones, then that's really just the definition of bias. There is already enough of that in the world.

It also gave Ashley the opportunity to provide even more information about this topic...

As was said... posts that you don't find useful... you should simply ignore. Someone, like myself, might very much appreciate it.

Encouragement. Not discouragement.

Hi All...

Still pretty new with C2, and I'm impressed.

One thing though, and maybe I am missing something, but I am used to being able to read & set *any* property of an object from code, that I can in the IDE (with a few exceptions).

I'm a bit frustrated so far in not being able to, for example, Read the text of a button. Its a property... so why is there not a MyButton.text property to read? There is a method to set it... so I'm just a bit puzzled.

It's the little things. Having the basic functionality "rounded out" and very uniform across the system would help quite a lot. A less idiosyncratic environment.

Now, again... if I'm missing something, please let me know. It may all just be my ignorance.

Regards,

R