Unofficial Mojo FAQ

Freddie - feature request: can you add the option to wrap the monitors in mouse over settings and/or to add the same monitor more than once: when I setup 3 PCs next to each other I'd like that when I reach one on the far left or far right if I continue that way it wraps back to the other one instead of having to go all the way back

Generalizing I suppose it may be convenient too to be able to put some slave both say on the right and below a given one so I can choose to path to get them

But for now a simple "wrap" check box would be nice (automatically join the left most with the right most edges)

ps: that dialog has a small bug; it has a greyed out version of the "bring home" hotkey setting (found in the other dialog) : remove it or make it work ?

Quote:

---

Originally Posted by Moorea

Freddie - feature request: can you add the option to wrap the monitors in mouse over settings and/or to add the same monitor more than once: when I setup 3 PCs next to each other I'd like that when I reach one on the far left or far right if I continue that way it wraps back to the other one instead of having to go all the way back

---

You can add this to the request list but I'll tell you now, it's unlikely that I'll get to this for a long time because I would have to make some major changes to a complicated part of the program and since eventually I want to rewrite that code anyway, I'm going to put off changing it until I do the rewrite.

Quote:

---

ps: that dialog has a small bug; it has a greyed out version of the "bring home" hotkey setting (found in the other dialog) : remove it or make it work ?

---

That's not a bug. It's just half-finished. I can't do the other half of the work until I finish rewriting the configuration data structures.

The program is going to have visible half-finished features sprinkled all over the place for a long time. This is an alpha test.

This is exactly what I meant the other day when I said I had better maintain the bug list myself because other people can't tell whether something is a bug or is merely unfinished.

It's ok we can wait

About bugs vs unfinished - it's still useful to have a list of known issues so people don't spend time wondering about the same things over and over again or if they need to report it - also the reason why I called that one a bug is you do have the other part of the UI (and conf) where that setting is working - either way I don't think the same setting should be in 2 places - but again this is "small"

Quote:

---

Originally Posted by Moorea

About bugs vs unfinished - it's still useful to have a list of know issues so people don't spend time wondering about the same things over and over again or if they need to report it

---

Yes but I have to do it.

Quote:

---

- also the reason why I called that one a bug is you do have the other part of the UI (and conf) where that setting is working - either way I don't think the same setting should be in 2 places - but again this is "small"

---

If you don't like the design of something, I recommend that you tell me, "I don't like this design."

I put this setting in both places because (1) it has to go on Predefined Hotkey Settings but (2) many people who use mouseover will only think of looking on Mouseover Settings.

I have no choice about (1). If I omit it from (2), a signficant number of people will look on (2), see that it's not there, and conclude that Mojo is a shitty program.

In general, I think that putting settings in multiple places makes the program easier to use, and there isn't any downside.

k agreed - the only downside is then, why it works in once place and not in the other :-) but that can wait

Where do you maintain the list of open issues ?
(maybe Fur/Svper can change the ownership of the 3rd post so it's yours to edit... or I can repost the first 2 in a new thread and you can maintain the 3rd one as open issues)

Quote:

---

Originally Posted by Moorea

Where do you maintain the list of open issues ?

---

I think I started one on Google but I"m not going to continue it.

I'll probably make a new one on mojoware.org but I'm not sure how soon I'll get to it.

Quote:

---

Originally Posted by Moorea

k agreed - the only downside is then, why it works in once place and not in the other :-) but that can wait

---

Why it works? Do you mean why it must be in one place but not necessarily the other? Because the list of Predefined Hotkeys says "Predefined Hotkeys" at the top.

People wil assume that it's a complete list, so it has to be complete. I can't omit any predefined hotkeys from it.

no I was just reiterating that I don't quite understand why the feature (setting a home key hotkey) is working fine when in the predefined hotkeys dialog and disabled in the mouseover dialog - unless somehow "bringing mouseover cursor home" and "hotkey for bringing back cursor" are 2 different things that aren't actually supposed to be the same and the later is the unfinished one ?

It's not working on Mouseover Settings because there isn't any code to modify that setting in the file that implements that dialog box.

I can't use the code from Predefined Settings because that code deals with a whole block of config info.

Since I wrote the code in Predefined Settings, I decided to rewrite the data structures that are used for config info, so I will have to rewrite the code in Predefined Settings.

After I rewrite that code, I will write new code for Mouseover Settings.

One of the reasons I decided to rewrite the data structures is to make it easy to write the code for that setting on Mouseover Settings.

In short, that item is waiting (like so many other things in the program) for me to rewrite the configuration data structures. They are pretty complicated. They exist in three forms -- serialized on TCP, serialized in files, and in memory -- and I want to make sure I get them right, since future work on the program will be very fun and easy if they are well designed but not so fun if they are not.

k thx for the explanation.

Speaking of the dialog, having the text field look like an editable one (white and you can click in it and get a cursor) is slightly bad user experience given that you can't actually type in it - the only benefit seems to be to select words to copy out but I don't think that's worth the user surprise of nothing happening when typing in there (unless you want later that typing in there actually works as a simpler version of the more complete dialog you get when clicking "set") - just my 2 cents

Quote:

---

Originally Posted by Moorea

k thx for the explanation.

Speaking of the dialog, having the text field look like an editable one (white and you can click in it and get a cursor) is slightly bad user experience given that you can't actually type in it - the only benefit seems to be to select words to copy out but I don't think that's worth the user surprise of nothing happening when typing in there (unless you want later that typing in there actually works as a simpler version of the more complete dialog you get when clicking "set") - just my 2 cents

---

Let's wait and see what other people think.

I'll just point out that if that field (and similar fields on Predefined Hotkeys) were gray, they woud be hard to read.

make it white but not have a visible cursor when clicked?

Good idea. I'll try to do that.

Added "Repeater regions (clicks in one window part actually go to some other window) - useful for healbot mapping" to wish list (from http://www.dual-boxing.com/showthrea...8193&page=2#14 )