Opened 16 years ago
Last modified 5 years ago
#2864 assigned bug
after mounting, disk icons overlap on desktop
Reported by: | Adek336 | Owned by: | leavengood |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Applications/Tracker | Version: | R1/Development |
Keywords: | Cc: | mdisreali@… | |
Blocked By: | Blocking: | #473, #6432, #7775, #14417 | |
Platform: | All |
Description
When I mount a disk it is very often that it's icon overlaps with the Trash or another disk's icon.
Attachments (7)
Change History (19)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
Component: | User Interface → Applications/Tracker |
---|---|
Owner: | changed from | to
Version: | R1/pre-alpha1 → R1/Development |
It shouldn't be too hard noticing this, and move the new icon someplace else - the new position shouldn't even be stored before the user manually changes it again.
comment:3 by , 14 years ago
Cc: | added |
---|
Is it possible for Tracker to "know" if it is placing icons on top of another? If so, could logic be added so that Tracker moves the new volume icon to the right?
follow-up: 5 comment:4 by , 14 years ago
Users can actually make icons overlap themselves. So even while Tracker can figure out if a mounted volume overlaps another icon, it can't be sure this is how the user actually configured it. In strict spatial mode, Tracker should never override user configured placement. I believe this should be fixed differently: Introduce an icon placement mode where the user can arrange icons on a grid only and never so that they overlap. If this mode is preferred by everyone, the current mode could then be competely replaced by it.
comment:5 by , 14 years ago
Replying to stippi:
Users can actually make icons overlap themselves. So even while Tracker can figure out if a mounted volume overlaps another icon, it can't be sure this is how the user actually configured it.
I have actualy noticed that the stored position is not always the position at witch the icon of a mounted disk is placed, especialy if you are using significantly different versions of Open Tracker (though this does also some times happen using only the same version).
The Tracker code is to big and convaluted for me to learn quickly enough to be able to figure out what is causing this.
by , 13 years ago
Attachment: | SenryuPE-0.5g-is-masking-a-file.png added |
---|
This is still valid in hrev42190. Mounted Blank_BFS and SenryuPE-0.5g, and the latter was located in the wrong place
by , 13 years ago
Attachment: | disk-ordered.png added |
---|
Here Blank_BFS and SenryuPE-0.5g are after the manual move of the SenryuPE-0.5g disk icon.
comment:7 by , 13 years ago
I am using VMWare version of Haiku and there is some problem with the default settings, if you want to install also a SenryuPE-0.5g disk. In default settings CD-ROM is in the wrong place and if I only append the SenryuPE-0.5g settings, I cannot launch the VMWare Player at all. I will enclose here the present settings file and the fixed settings file with the CD-ROM disk and SenryuPE-0.5g disk.
by , 13 years ago
Attachment: | haiku-alpha.vmx added |
---|
Here is the orginal VMWare settings with a CD-ROM but without a SenryuPE-0.5g disk.
by , 13 years ago
Attachment: | fixed-haiku-alpha.vmx added |
---|
Here is the fixed VMWare settings file with CD-ROM and SenryuPE-0.5g. I do not know, if the order of settings will cause also disk icon problems.
by , 13 years ago
Attachment: | fixed-haiku-alpha.2.vmx added |
---|
Here is the fixed VMWare settings file with CD-ROM and SenryuPE-0.5g. I do not know, if the order of settings will cause also disk icon problems.
by , 13 years ago
Attachment: | fixed-haiku-alpha.3.vmx added |
---|
Here is the fixed VMWare settings file with CD-ROM and SenryuPE-0.5g. I do not know, if the order of settings will cause also disk icon problems.
by , 13 years ago
Attachment: | Senryu-is-active.png added |
---|
Another problem: Why SenryuPE-0.5g disk is active?
comment:8 by , 13 years ago
Blocking: | 7775 added |
---|
comment:9 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:10 by , 6 years ago
Blocking: | 14417 added |
---|
comment:11 by , 5 years ago
Blocking: | 473 added |
---|
comment:12 by , 5 years ago
Owner: | changed from | to
---|
What is odd is that Tracker does have code to try to deal with this. But clearly it does not work. So it may be a very minor and easy fix after some debugging. I will take a look while I am working on Tracker.
The icon position is remembered as attributes on the mounted drive itself. So this behavior is consistent with other icons. I am undecided about it, since I don't like the mess either.