[Home] [Downloads] [Search] [Help/forum]

Gammon Software Solutions forum

See www.mushclient.com/spam for dealing with forum spam. Please read the MUSHclient FAQ!

[Folder]  Entire forum
-> [Folder]  MUSHclient
. -> [Folder]  Miniwindows
. . -> [Subject]  MouseDown Problems. Baffled. (Python)
Home  |  Users  |  Search  |  FAQ
Username:
Register forum user name
Password:
Forgotten password?
(New message)
Subject: MouseDown Problems. Baffled. (Python)
Name:
Your forum user name.
Register forum user name
Password:
Your forum password.
Forgotten password?
Message:
Message to be posted (in English, please)
Maximum of 6000 characters. Text only please, no HTML.
Forum codes:
Check this if your message uses 'forum codes' or templates (auto-detected for new posts).
Forum codes Templates

Save this message ...

Subject review (reverse sequence)

Posted by Alca   (20 posts)  [Biography] bio
Date Sat 31 Oct 2009 04:17 PM (UTC)  [ quote  ]
Message
WindowShow() works splendidly. It was really a dumb error on my part. Because both double-clicking and adding a world.Note seemed to force the window to be redrawn, I just thought there was way more behind this than there actually is.

Thanks for all the help, guys. You must have way too much patience...
[Go to top] top
Posted by Nick Gammon   Australia  (18,770 posts)  [Biography] bio   Forum Administrator
Date Fri 30 Oct 2009 09:27 PM (UTC)  [ quote  ]
Message
Those documentation changes have now been applied to the online documentation here. For example:

Template:function=WindowDrawImage WindowDrawImage

The documentation for the WindowDrawImage script function is available online. It is also in the MUSHclient help file.

- Nick Gammon

www.gammon.com.au, www.mushclient.com
[Go to top] top
Posted by Nick Gammon   Australia  (18,770 posts)  [Biography] bio   Forum Administrator
Date Fri 30 Oct 2009 08:19 PM (UTC)  [ quote  ]
Message
I have amended the help file for the next version to make it more obvious that you need to call Redraw after changing a miniwindow's contents.
- Nick Gammon

www.gammon.com.au, www.mushclient.com
[Go to top] top
Posted by Nick Gammon   Australia  (18,770 posts)  [Biography] bio   Forum Administrator
Date Fri 30 Oct 2009 08:05 PM (UTC)  [ quote  ]
Message
See this comment under WindowShow:

Quote:

Calling WindowShow forces a window refresh, so the screen will be updated with the new miniwindow (or absence, as the case may be).

If you have changed the miniwindow, you may not want to call WindowShow (in case they currently want it hidden). In this case you can call Redraw () instead, to cause the main output window to be redrawn, without changing the status of any miniwindows.

- Nick Gammon

www.gammon.com.au, www.mushclient.com
[Go to top] top
Posted by Nick Gammon   Australia  (18,770 posts)  [Biography] bio   Forum Administrator
Date Fri 30 Oct 2009 08:04 PM (UTC)  [ quote  ]
Message
WindowShow should be enough. The repaint happens quite quickly, next time through the main event loop (unless there are other higher-priority events, like mouseclicks there). Getting into the habit of putting Repaint everywhere will slow the program down for no noticeable improvement.


Alca said:

I still think it behaved weird, but at least now it works.


It is quite valid to draw to offscreen windows, so automatically repainting the onscreen ones just because you draw an image would add an overhead that might not be justified.

BTW, had you simply covered the MUSHclient window up (eg. with a notepad) and uncovered it, that should have forced a repaint, making it more obvious that the problem was not some bizarre script issue, but that the window was not being redrawn.
- Nick Gammon

www.gammon.com.au, www.mushclient.com
[Go to top] top
Posted by WillFa   USA  (517 posts)  [Biography] bio
Date Fri 30 Oct 2009 06:01 PM (UTC)  [ quote  ]
Message
Try adding a world.WindowShow("name") and a world.Repaint() to the function.

If WindowDrawImage follows with the other Window functions, you're actually manipulating a buffer and not the region of the screen itself. You'd need the WindowShow to "apply" the changes. After the changes are applied, they don't appear until the screen gets redrawn -- for example from a world.Note() or incoming text from the mud. Repaint should force an update.
[Go to top] top
Posted by Alca   (20 posts)  [Biography] bio
Date Fri 30 Oct 2009 10:11 AM (UTC)  [ quote  ]

Amended on Fri 30 Oct 2009 01:59 PM (UTC) by Alca

Message
This code is entirely in a plugin. Error checking gives a zero, so no drawing error. Changing names didn't work either. For the moment, I'm stuck with adding an empty line via world.Note, but it's not aesthetically pleasing >.>

Next I'll try to work with one mousedown function with ifs for different hotspot_ids. Maybe that'll work.

Edit:: It didn't. However, I noticed that it does react to double-clicking. Checking my code now, maybe I'll find something. And if not, maybe I can code a solution now.

Edit2:: Bah. Stupid me. Somehow I managed to delete the WindowShow function that was supposed to be called. I still think it behaved weird, but at least now it works. Thanks for the help.
[Go to top] top
Posted by Nick Gammon   Australia  (18,770 posts)  [Biography] bio   Forum Administrator
Date Thu 29 Oct 2009 10:31 PM (UTC)  [ quote  ]

Amended on Thu 29 Oct 2009 10:32 PM (UTC) by Nick Gammon

Message
Alca said:

Edit:: my spacing seems to be off in this example, this is not the case in the actual code though.


Template:codetag To make your code more readable please use [code] tags as described here.


Is this code in a plugin? Hotspots only work in plugins.

Alca said:

It's definately not a drawing error. I don't even get an error, it just, you know, fails to work.


See:

Template:function=WindowDrawImage WindowDrawImage

The documentation for the WindowDrawImage script function is available online. It is also in the MUSHclient help file.



That returns a non-zero code if it fails. You could test that code and display a message if it is not zero. That at least eliminates that possibility.

eg.


def Loot_ButtonClicked():
   iStatus = world.WindowDrawImage(winid, "Loot1_clicked", 66, 1, 0, 0, 1, 0, 0, 0, 0)
   if iStatus != 0:
    world.note ("Error code from WindowDrawImage: " + iStatus)


(or however you do it in Python).

However I can't really explain it. Maybe the Python experts here can.

- Nick Gammon

www.gammon.com.au, www.mushclient.com
[Go to top] top
Posted by Alca   (20 posts)  [Biography] bio
Date Thu 29 Oct 2009 09:38 PM (UTC)  [ quote  ]

Amended on Thu 29 Oct 2009 10:20 PM (UTC) by Nick Gammon

Message
Adding an empty line doesn't solve the problem, unfortunately. Empty lines generally don't do much in Python, spaces do, and those are all fine.


This function doesn't work:


def Loot_MouseDown(flags, hotspot_id):
    Loot_ButtonClicked()
    return 0


This one does:


def Loot_MouseDown(flags, hotspot_id):
    world.Note("Check 1")
    Loot_ButtonClicked()
    return 0


This function is called as the hotspot "mousedown" handler, just so you know, though I don't see how that would change anything.

Loot_ButtonClicked() calls the following:


def Loot_ButtonClicked():
    world.WindowDrawImage(winid, "Loot1_clicked", 66, 1, 0, 0, 1, 0, 0, 0, 0)


It's definately not a drawing error. I don't even get an error, it just, you know, fails to work.

I'm going to try different names, maybe Python won't accept the current ones or something strange...

Edit:: my spacing seems to be off in this example, this is not the case in the actual code though.
Edit2:: added the code for Loot_ButtonClicked()
[Go to top] top
Posted by Nick Gammon   Australia  (18,770 posts)  [Biography] bio   Forum Administrator
Date Thu 29 Oct 2009 08:04 PM (UTC)  [ quote  ]
Message
I'm no Python expert, but can you post the function in its working and not-working version (the part that handles the mousedown).

Isn't Python very spacing-conscious? Maybe by adding an extra line you changed the way it handled the function.

Also I would check the return code from the line that draws the image - if a drawing function fails it generally returns a non-zero error code.
- Nick Gammon

www.gammon.com.au, www.mushclient.com
[Go to top] top
Posted by Alca   (20 posts)  [Biography] bio
Date Thu 29 Oct 2009 04:58 PM (UTC)  [ quote  ]

Amended on Thu 29 Oct 2009 04:59 PM (UTC) by Alca

Message
I'm toying around with hotspots, and I managed to get a button working just fine.

Then I decided I needed another button. Which also works.
Except for one thing.

I want my buttons to draw a different image on MouseDown, so it shows you're clicking on it. This worked just fine in my first version, but doesn't now.

Which is already weird, since my code hasn't changed.

However, it gets weirder.

When adding a world.Note to the function that handles the drawing of the 'clicked' image, it works. Splendidly. Deleting that world.Note reverses everything to its problematic state.

I'm baffled, as I have absolutely no idea what causes this.

[Go to top] top

The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).

To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.

2,542 views.

[Reply to this subject]  Reply to this subject   [New subject]  Start a new subject   [Refresh] Refresh page

Go to topic:           Search the forum

[Go to top] top

[Home]

Written by Nick Gammon - 5K

Comments to: Gammon Software support
[RH click to get RSS URL] Forum RSS feed ( http://www.gammon.com.au/rss/forum.xml )

[Best viewed with any browser - 2K]    [Internet Contents Rating Association (ICRA) - 2K]    [Web site powered by FutureQuest.Net]