It's fixed but I'm going to change the window a little bit before i post it. about 20 min.
Printable View
It's fixed but I'm going to change the window a little bit before i post it. about 20 min.
That's not a bug. "Use system setting" really means "Mojo doesn't do anything." You won't get your system defaults back till you reboot.Quote:
Originally Posted by Fursphere
Maybe there's a better name than "Use system defaults" for those buttons.
Edit: The problem is, Mojo has no way to know what your system defaults are They are probably in the registry but Microsoft doesn't document them (at least I don't think it does) and I don't lke using undocumented features.
Edit: Maybe just this once I'll use undocumented settings. :)
Build 20 is up.
Fur, you're right, that "Use system setting" stuff doesn't cut it.
I'll have to figure out tomorrow what to do about it.
It's amazing how tiny things like this turn into problems. :)
This whole feature should have taken 45 minutes. :)
Here's my proposed solution for "Use system settings."
When Mojo starts up, it will record the settings that were in use before it started.
If you select "Use system settings," Mojo will restore those settings.
Maybe the caption should say "Use prior settings" or something like that.
Maybe the caption should say "Restore something or other."
"Restore original settings."
"Use existing settings."
"Use current settings."
Would it be better to store the settings that were in use whenever the user changes the setting off of "Use system default", rather than when the program starts?Quote:
Originally Posted by Freddie
That would prevent conflicts if the user changed the Windows setting between starting Mojo and changing the setting in Mojo.
Maybe I'll do it that way.
I don't mind having to reboot to get back to system default if it's hard to remember and it wouldn't be the same (ie it would change something from default) - don't sweat that part too much
now the radio buttons do all work ! thx a lot !
small suggestion: add an "apply" button so the user can experiment with the settings without having to click "ok" and reopen the dialog between each try
thanks a lot for that feature and quick turn around !
another minor nit picking (but I wouldn't sweat it either) the raise window part doesn't work if the first on is on off (so I guess in theory it should be grayed out in that case)
[I know it's not a mojo feature but you're doing the UI for microsoft :-) ]
minor unrelated bug report: I tried to assign NumLock to toggle broacasting on/off so I get some visual feedback on my keyboard (pending the overlay or semi transparent status window :p) but if I do it eats the event and my keyboard light doesn't toggle anymore
(tried to put both nothing and "when numlock is on" which didn't work; and pressed "numlock" which worked (toggles it in mojo) but then doesn't toggle the light on my keyboard anymore
another interesting side effect/bug of this new feature:
when I mouse to the other PC's screen, mojo comes to the foreground on my main PC, even if the mouse doesn't at all go over mojo's window while moving out of the 1st pc' screen (seems like when you hide the local cursor; you put it maybe on mojo's and that raise that window - can you leave it at the last window it was in on the original computer screen?)
sorry for all the issue reports :-) don't be discouraged :-)
To save time, I've been omitting Apply buttons from all settings boxes. I'll add them in at some future time.Quote:
Originally Posted by Moorea
Maybe I'll add them today since you reminded me.
I agree. The problem is that if the "do nothing" buttons work that way, it's hard to give them names that make their function clear. But when I woke up this morning, a possible answer popped into my head:Quote:
Originally Posted by Moorea
-- Do not change
-- Turn off
-- Turn on
During mouseover the local cursor has to be handled in a pretty complicated way. It's not just parked. It's moving, it's on top of a special invisible window, it's constantly moving away from the center of the screen and getting recentered, etc.Quote:
Originally Posted by Moorea
Edit: I just looked at the source code and this doesn't seem to be true. I think I was remembering a different version I wrote earlier. I'm not sure why this problem is happening.
I'll try to figure out a way to fix this.
I'm not discouraged. I'm glad you're noticing all this stuff.Quote:
sorry for all the issue reports :-) don't be discouraged :-)
You probably feel like you're dumping work on me but my reaction is the exact opposite.
My reaction is, "Oh good, I don't have to spend time testing, because Moorea will tell me about errors."
I think that's important. I"m glad you pointed it out.Quote:
Originally Posted by Moorea
If I don't change that, people will report it as a bug, because they'll say "raise window" isn't working. I'll change it.