right mouse click

7Snails

Charles12310 wrote:
7Snails wrote:
Support. There used to be a workaround in Scratch 1.4, but it has been since patched
What was this workaround?

Here is a link to what someone posted about it (it's really simple) https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/24971/?page=1#post-223377

FancyFoxy

7Snails wrote:
Charles12310 wrote:
7Snails wrote:
Support. There used to be a workaround in Scratch 1.4, but it has been since patched
What was this workaround?
Here is a link to what someone posted about it (it's really simple) https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/24971/?page=1#post-223377

Oh… so this is a duplicate…
Huh.

andyhanwu

the middle (scroll) is actually left and right arrows.

AwesomeSmilee

I think the reason this hasn't been added earlier is because Flash can't handle it.
I mean, right-click is such a simple suggestion - shouldn't they have added it earlier? So there must be another reason.

EDIT: wrong wrong wrong Flash can handle it fine

Last edited by AwesomeSmilee (Aug. 5, 2017 14:08:16)

Charles12310

I forgot, if both parts of the mouse are down:

<mouse [both v] down? :: sensing >

So, I think these are what should replace the mouse down block:

<mouse [left v] down? :: sensing >

<mouse [right v] down? :: sensing >

<mouse [both v] down? :: sensing >

We don't need a mouse none down block because we just need this:

<not <mouse [choose v] down? :: sensing >>

Instead of:

<mouse [none v] down? :: sensing >

Last edited by Charles12310 (July 11, 2017 17:45:41)

7Snails

Charles12310 wrote:
I forgot, if both parts of the mouse are down:
<mouse [both v] down? :: sensing >
So, I think these are what should replace the mouse down block:
<mouse [left v] down? :: sensing >

<mouse [right v] down? :: sensing >

<mouse [both v] down? :: sensing >
We don't need a mouse none down block because we just need this:
<not <mouse [choose v] down? :: sensing >>
Instead of:
<mouse [none v] down? :: sensing >

<mouse [both v] down? :: sensing >

Would be unnecessary.

<<mouse [left v] down? :: sensing > and <mouse [right v] down? :: sensing >>

Last edited by 7Snails (July 11, 2017 18:01:03)

Charles12310

7Snails wrote:
Charles12310 wrote:
I forgot, if both parts of the mouse are down:
<mouse [both v] down? :: sensing >
So, I think these are what should replace the mouse down block:
<mouse [left v] down? :: sensing >

<mouse [right v] down? :: sensing >

<mouse [both v] down? :: sensing >
We don't need a mouse none down block because we just need this:
<not <mouse [choose v] down? :: sensing >>
Instead of:
<mouse [none v] down? :: sensing >
<mouse [both v] down? :: sensing >
Would be unnecessary.
<<mouse [left v] down? :: sensing > and <mouse [right v] down? :: sensing >>

Yeah, but that doesn't mean it can't be added.

Also we don't need to use more than one block if it means combination.

LionHeart70

Charles12310 wrote:
7Snails wrote:
Charles12310 wrote:
I forgot, if both parts of the mouse are down:
<mouse [both v] down? :: sensing >
So, I think these are what should replace the mouse down block:
<mouse [left v] down? :: sensing >

<mouse [right v] down? :: sensing >

<mouse [both v] down? :: sensing >
We don't need a mouse none down block because we just need this:
<not <mouse [choose v] down? :: sensing >>
Instead of:
<mouse [none v] down? :: sensing >
<mouse [both v] down? :: sensing >
Would be unnecessary.
<<mouse [left v] down? :: sensing > and <mouse [right v] down? :: sensing >>
Yeah, but that doesn't mean it can't be added.

Also we don't need to use more than one block if it means combination.

Exactly, even though “go to front” has a simple workaround that looks like this:

go back (-999) layers

it's still staying.

FancyFoxy

LionHeart70 wrote:
Charles12310 wrote:
7Snails wrote:
Charles12310 wrote:
I forgot, if both parts of the mouse are down:
<mouse [both v] down? :: sensing >
So, I think these are what should replace the mouse down block:
<mouse [left v] down? :: sensing >

<mouse [right v] down? :: sensing >

<mouse [both v] down? :: sensing >
We don't need a mouse none down block because we just need this:
<not <mouse [choose v] down? :: sensing >>
Instead of:
<mouse [none v] down? :: sensing >
<mouse [both v] down? :: sensing >
Would be unnecessary.
<<mouse [left v] down? :: sensing > and <mouse [right v] down? :: sensing >>
Yeah, but that doesn't mean it can't be added.

Also we don't need to use more than one block if it means combination.
Exactly, even though “go to front” has a simple workaround that looks like this:
go back (-999) layers
it's still staying.

Not if another object is more than 999 layers ahead, somehow…
But yeah, it does solve the problem of having more than 2 options in the drop-down.

Charles12310

LionHeart70 wrote:
Charles12310 wrote:
7Snails wrote:
Charles12310 wrote:
I forgot, if both parts of the mouse are down:
<mouse [both v] down? :: sensing >
So, I think these are what should replace the mouse down block:
<mouse [left v] down? :: sensing >

<mouse [right v] down? :: sensing >

<mouse [both v] down? :: sensing >
We don't need a mouse none down block because we just need this:
<not <mouse [choose v] down? :: sensing >>
Instead of:
<mouse [none v] down? :: sensing >
<mouse [both v] down? :: sensing >
Would be unnecessary.
<<mouse [left v] down? :: sensing > and <mouse [right v] down? :: sensing >>
Yeah, but that doesn't mean it can't be added.

Also we don't need to use more than one block if it means combination.
Exactly, even though “go to front” has a simple workaround that looks like this:
go back (-999) layers
it's still staying.

Solution:

go back ((0) - ((1)/(0))) layers

go back ((0) - ([10^ v] of (309) :: operators )) layers

go back ((0) - ([e^ v] of (1000) :: operators )) layers

Last edited by Charles12310 (July 12, 2017 01:41:56)

JustOscarJ2

Support this would be great!

Evan2963

Support

LionHeart70

I found a workaround, but making a general block for this would be more convenient;

when this sprite clicked
if <mouse down?> then 

  
set [mouse v] to [left]

else
set [mouse v] to [right]
end

But I'm not 100% sure if it still works..

Charles12310

LionHeart70 wrote:
I found a workaround, but making a general block for this would be more convenient;
when this sprite clicked
if <mouse down?> then 

  
set [mouse v] to [left]

else
set [mouse v] to [right]
end
But I'm not 100% sure if it still works..

Nah. It was removed. Besides, it only detects left click, or no click.

That's why I suggested:

<mouse [left v] down? :: sensing >

<mouse [right v] down? :: sensing >

To replace the mouse down block. I also suggested this:

<mouse [both v] down? :: sensing >

So that I don't need to put this:

<<mouse [left v] down? :: sensing > and <mouse [right v] down? :: sensing >>

Botcho_Otkho

removed

Last edited by Botcho_Otkho (July 13, 2020 16:42:10)

FancyFoxy

Bump

FancyFoxy

Bump

Charles12310

<mouse [right v] down? :: sensing >

<mouse [left v] down? :: sensing >

<mouse [both v] down? :: sensing >

// (So that you don't have to do):

<<mouse [left v] down? :: sensing > and <mouse [right v] down? :: sensing>>

Carriage

support

Charles12310

Charles12310 wrote:

<mouse [right v] down? :: sensing >

<mouse [left v] down? :: sensing >

<mouse [both v] down? :: sensing >

// (So that you don't have to do):

<<mouse [left v] down? :: sensing > and <mouse [right v] down? :: sensing>>

// Example:
if <mouse [right v] down? :: sensing > then
broadcast [open menu v]
else
if <mouse [left v] down? :: sensing > then
broadcast [click v]
end
end

Last edited by Charles12310 (July 31, 2017 19:36:56)

Discuss Scratch