MouseX(), MouseY()

BlitzMax Forums/BlitzMax Programming/MouseX(), MouseY()

The forum is locked. These are the original blitzbasic.com forums, kept so they can still be read. No new topics, replies or edits can be made here. To join in, head over to the Blitz3D+ forums.

What's against them?

IMHO here are the pros:
- can look more fancy
- can have major additional functionality
- can be more screen-efficient

cons:
- it's not according to the OS settings

The problems start when you're doing brutesque things like map-editors, gfx-editors and other things which are huge and where you need all the pixels there are at once. Often enough ppl have pumped-up titlebars, windowmenus and suddenly your app doesn't fit the window. Buttons with texts on them? What about people with big ugly fonts, then you get cut-off words. (that's why ppl want imagebuttons ever since B+, since icons are small, international and efficient :P)

The whole point is that the Windows interface is quite limited. I've made custom gadgets for years already, and just by combing LMB and RMB things, keyboard things and combinations, there're so much functionality to add to a single gadget. This extra functionality can actually replace a lot of other gadgets this way. A simple scrollbar for example is really far too simple, there're so many ways one can enhance a scrollbar with the aid of extra mouse functionality, keyboard functionality. My aim is to create flexible instruments out of gadgets, not just dull devices!

About the con, that it's not according to one's OS settings.. well, their OS settings might also not be according to the requirements of my app. And with evertone having different settings there's no telling what I should rely on. Rather than them ruining my interface, I rather have my own interface with guaranteed sizes and dimensions.