View Single Post
  #19  
Old October 26th 19, 12:10 AM posted to microsoft.public.windowsxp.general
J. P. Gilliver (John)[_7_]
external usenet poster
 
Posts: 603
Default desktop icons - change grid offset ?

In message , R.Wieser
writes:
John,

How many controls do you see in the below picture - and I don't mean the
ones in the caption bar of the window itself :
http://zetcode.com/img/gui/winapi/statictext.png


None.


There you have it. A problem with the definition of the word "control".

And is therefore not a "control", as most people would use the term.


I'm not "most people", and neither are you. Both of us have done "something"
in programming, using multiple languages even. But does it really matter ?


Well, I think it does; when I'm talking as a programmer, I might - but
as a user, and certainly for the benefit of anyone else still reading
(sorry if that sounds like Our Dear Friend!), I wouldn't. Call it a
control, that is.

We had a problem in communication, which now has been solved.


Not entirely (-:

I don't think I know anyone who would call a progress bar a control.


Actually, you've known someone who does, and for quite a while now: me. :-)


You know what I meant!

Also everyone who designs user interfaces (read: a window/dialog with stuff
on it) will. Most definitily if he's a programmer too. Microsoft has
always called them that (guess where I got my clue from), with an example
here :
https://docs.microsoft.com/en-us/win...guide/controls


Microsoft is well-known for going their own way, and changing the name
of things depending on the colour of the moon ...

In earlier posts, you said you were moving (what _you_ call, I now see) a
"control" that contains the icons. It now sounds as if you're referring to
something transparent, and thus probably invisible.


The control has been made invisible (actually, it simply does not erase its
background and has its border-drawing disabeled, meaning that whatever
should be behind it stays visible), not its contents (the icons).

I'm puzzled how you (a) move such a thing, (b) know that you've done so.


a) You use one of Windows own functions to tell the control to position
itself somewhere else (function in case: MoveWindow. Or SetWindowPos. Both
work).


Sounds like you are doing some programming here, or something like that.
When you said you were "moving a control", especially as you talked
about "icons falling off as you move it" (or something close to that), I
assumed you were dragging something with the mouse [i. e., to avoid
ambiguity, moving the mouse pointer over it with the button held down],
or touchpad equivalent]. Not typing parameters into something.

b) the icons that are placed on the control move with it. As the icons move
I know that the control must have moved. But, I've also, as a test, enabled
the controls build-in border-drawing (by flipping a single bit in its
"style" property). Seeing that border appear and change position when I
tell the control to move does give me some confidence that I actually did
so. :-)

Regards,
Rudy Wieser


2
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

The first banjo solo I played was actually just a series of mistakes. In fact
it was all the mistakes I knew at the time. - Tim Dowling, RT2015/6/20-26
Ads