I came in just do do a little jig over how happy I am about the Mousewheeel addition!
|
In response to Bravo1
|
|
Bravo1 wrote:
I came in just do do a little jig over how happy I am about the Mousewheeel addition! Don't lie. We all know you came to make a little love, too. Seriously though. I cannot wait to play with all these new features, and see what everyone does with them. I think a whole row or two of doors just swung open. |
A note on MouseWheel: the webclient currently suffers from a standardization problem in that department, because browser makers are stupid and couldn't get their crap together. I'll figure it out eventually. My plan is to make the webclient adhere to the same standard where 120 is a full "tick".
508.1288 is up now. |
In response to Kidpaddle45
|
|
In response to Lummox JR
|
|
Lummox JR wrote:
My plan is to make the webclient adhere to the same standard where 120 is a full "tick". Sorry to bring up an old argument, but I should ask this while the feature is new: Why choose to display more magic numbers in BYOND instead of some form of read-only value? =) |
In response to ACWraith
|
|
ACWraith wrote:
Lummox JR wrote: Do you mean like a const or a #define in stddef.dm? I'd be on board with that, though I want to see if I can standardize the webclient first. I suppose on some level it might make sense to handle it in terms of a fraction, where it'd be a float value like 1 or 0.5 or something, although sticking with ints is probably smarter if the range isn't a power of 2. |
In response to Lummox JR
|
|
Lummox JR wrote:
Do you mean like a const or a #define in stddef.dm? I'd be on board with that, though I want to see if I can standardize the webclient first. Yeah, something like that. There's also the option of a function if it turns out you can't standardize something. In this instance, perhaps the wheel delta range could be a read-only value of the client set automatically when it logs in? Then standardization might be moot. (Honestly, it might be nice to have client constants/properties instead of globals anyway.) |
In response to Lummox JR
|
|
On my laptop's touchpad, two-finger scrolling gives values of as little as 3, for smooth scrolling.
|
In response to Kidpaddle45
|
|
In response to Ter13
|
|
Yeah, it works by changing the icon-size or zoom parameters of the map control. For efficiency, you'll probably want to modify client.view too, to make sure you're not asking the server for more than you can actually see.
|
In response to MDC
|
|
MDC wrote:
Exentriks Gaming wrote: I will personally perform sexual services for Lummox if this gets fixed soon. |
:) Love seeing some the makeovers as people come back and dabble with the new features.
|
That's sort of what I man. I come from C#, so I've used things like the following before:
Then, if something like an InvalidOperation exception pops up, it doesn't get caught, and is bubbled up. Being able to rethrow errors without wrecking the stack trace is meant to be an analogue to that.