MK <murat@compuplus.net> writes:

> On June 22, 2023 at 3:14:24 PM UTC-6, Axel Reichert wrote:
>
>> https://en.wikipedia.org/wiki/Anonymous_pipe
>
> Philippe was talking about "named pipes" and
> you give a link to "anonymous pipes". They are
> not the same.

Thanks. I know how pipes work. I was thinking about referring you to

https://en.wikipedia.org/wiki/Pipeline_(Unix)

instead, which covers the general case, but could already hear your
complaints: "I asked about Windows".

> Why do you always complicate the discussion with things that are
> not essential to the subject..? :(

It is not essential to your subject whether the pipes are named or
anonymous, so who is complicating the discussion?

Anyway, it is (again) time to temporarily lower your score for half a
year or so. rec.games.backgammon will be much more pleasant this way.

Axel

On June 23, 2023 at 12:11:25 AM UTC-6, Axel Reichert wrote:

> MK <mu...@compuplus.net> writes:

>> The idea was to prevent the bot from looking
>> at the upcoming dice rolls before it makes its
>> cube decision.

> See roll.c for whether this happens.

Don't you think Philippe was smart enough to
tell me this..!?

You seem to be too dense to follow what was
said for what reason during the discussion. :(

Go back to the beginning of the thread and read
slowly, carefully; making an effort to give the
other guy some credit for having a good reason
to have said what he has said.

>> idea is to give each dice roll to the bot after
>> it finishes its cube decision.

> The bot asks for the dice roll after its cube
> decision, see roll.c.

See my above advice to you. It will help you.

MK

On June 23, 2023 at 12:20:47 AM UTC-6, Axel Reichert wrote:

> MK <mu...@compuplus.net> writes:

>> On June 22, 2023 at 3:14:24 PM UTC-6, Axel Reichert wrote:

>>> https://en.wikipedia.org/wiki/Anonymous_pipe

>> Philippe was talking about "named pipes" and
>> you give a link to "anonymous pipes". They are
>> not the same.

> Thanks. I know how pipes work. I was thinking
> about referring you to
> https://en.wikipedia.org/wiki/Pipeline_(Unix)

I couldn't read your mind to know what you had
intended. I can only go by what you wrote. But
this isn't even critical to show you don't know
how pipes work, neither in Unix nor Windows.

> instead, which covers the general case, but
> could already hear your complaints: "I asked
> about Windows".

The syntax may be different but I would guess
that the implementation if the same in both.

>> Why do you always complicate the discussion
>> with things that are not essential to the subject..? :(

> It is not essential to your subject whether the
> pipes are named or anonymous, so who is
> complicating the discussion?

Only anonymous pipes are blocked by nature,
because only their child processes can read
from them.

Named pipes can be blocked or not depending
on the parameters specified when opening and
writing/reading them. If they are not blocked,
then the reader can get an EOF as I had said in
my previous post.

I don't know how Noo-BG reads a pipe. I would
guess that in unblocked mode like a text dice
file. Phillip may know. Ask him. Also ask him
why he gave an exaample using named pipes.
You may lean something... You don't know
what you are talking about and still insist to
waste everyone's time with your Wikipedia
knowledge... :(

> Anyway, it is (again) time to temporarily
> lower your score for half a year or so.
> rec.games.backgammon will be much
> more pleasant this way.

I really don't know what you mean by this but
there is always the adage to take one's own
advice. Thus, I figure that I can't go too much
wrong by giving it to you...

MK

On November 25, 2023 at 7:29:51 AM UTC-7, Benno Maul wrote:

> Just one idea if you want to use your "own" dice.
> You could use the manual dice and an AHK
> Autohotkey script to observe, when the dice
> input window opens then the script runs any
> random generator to determine the row and
> column to perform a mouseclick to choose
> the dice.

Thanks for the idea. I posted a few times about
this and I never said it couldn't be done sending
mouse clicks but only pointed out how sending
key strokes is so trivially easier, even compared
to sending a single mouse click anywhere on a
window.

Noo-BG windows, including the dice input dialog,
are resizable and/or relocatable which makes it
so much harder to determine the coordinates of
dice images.

Have you ever tried it yourself? Do you have a
working script that you can share?

MK

MK schrieb am Sonntag, 26. November 2023 um 04:39:51 UTC+1:
> On November 25, 2023 at 7:29:51 AM UTC-7, Benno Maul wrote:
>
> > Just one idea if you want to use your "own" dice.
> > You could use the manual dice and an AHK
> > Autohotkey script to observe, when the dice
> > input window opens then the script runs any
> > random generator to determine the row and
> > column to perform a mouseclick to choose
> > the dice.
> Thanks for the idea. I posted a few times about
> this and I never said it couldn't be done sending
> mouse clicks but only pointed out how sending
> key strokes is so trivially easier, even compared
> to sending a single mouse click anywhere on a
> window.
>
> Noo-BG windows, including the dice input dialog,
> are resizable and/or relocatable which makes it
> so much harder to determine the coordinates of
> dice images.
>
> Have you ever tried it yourself? Do you have a
> working script that you can share?
>
> MK

Something like this. Hope this helps. You have to adjust the Rows and Columns to your screen and window size. The problem is, that the Dice window contains different text. For example the opening throw. But when you have set it to the center of the buttons it should work everytime.

#NoEnv
SendMode Input

#Persistent
Rows := [95,185,275,365,455,545]
Columns := [152,302,452,602,752,902]
SetTimer, ActiveDice, 500
return

ActiveDice:
if WinExist("GNU Backgammon - Dice")
{
Random, randX, 1, 6
Random, randY, 1, 6
MouseClick , Left , Columns[randX], Rows[randY]
Sleep 2000
}
return

On November 26, 2023 at 10:58:02 AM UTC-7, Benno Maul wrote:

> MK schrieb am 26. November 2023 um 04:39:51 UTC+1:

>> Noo-BG windows, including the dice input dialog,
>> are resizable and/or relocatable which makes it
>> so much harder to determine the coordinates of
>> dice images.

>> Have you ever tried it yourself? Do you have a
>> working script that you can share?

> Something like this. Hope this helps.

"Something like this" is hardly a good enough effort.
Your sample script won't work as is. It will require a
lot more effort to make it work even if windows stay
static in location and size.

> You have to adjust the Rows and Columns to your
> screen and window size.

You probably found the rows/colums array constants
using a utility or script which is additional effort even
if your windows remain always static.

Also, I'm not sure if screen size matters but you need
to set the "CoordMode" relative to the active control,
(excluding the window title), instead of to the default
which is relative to screen, to begin with.

> The problem is, that the Dice window contains
> different text. For example the opening throw.

Yes, opening roll window is wider due to vertical text
added but things may still work since dice icons are
wide enough. Yet this is not the only nor the worst of
your problems that you would have discovered if you
had actually tried to come up with a "working" code.

> But when you have set it to the center of the buttons
> it should work everytime.

I don't know what you mean by this nor how you would
accomplish it, which obviously would require still more
effort, but it won't work anyway.

If everything in the dice dialog resized proportionately,
you could change your rows/colums array constants
to percentages of the window size, which you would
have to find using the ControlGetPos function that in
itself being yet additional effort; (and that in addition
to figuring out the incremental ratios from Noo-BG's
documentation or source code which may take quite
more time and effort also).

But what is worse is that, when you resize Noo-BG's
main window, the dice window resizes automatially
also yet the dice icons don't resize at the same rate
as the spaces and other items around them. (I could
but I won't bother to mention that the dice window
can be resized only vertically or only horizontally since
that would almost never happen and since the above
problems are already enough to make creating a AHK
script, (or any other script), an impossible task.

With all this said, it's beyond comprehension why the
mother-loving stubborn jerks of the Noo-BG team are
refusing to implement keyboard imput for dice rolls,
which would take adding a minimal and trivial code.

MK