Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
47 user(s) are online (40 user(s) are browsing Forums)

Members: 0
Guests: 47

more...

Support us!

Headlines

 
  Register To Post  

Workbench Arexx port - access the path of an icon
Just can't stay away
Just can't stay away


See User information
When you select an icon byname it can happen that you have 2 (or more) identically named icons.
To be sure you use the right one you need at least their paths.

How can you acces these from a script?

Go to top
Re: Workbench Arexx port - access the path of an icon
Not too shy to talk
Not too shy to talk


See User information
This should give you the path to your selected icon:

options results
GETATTR WINDOWS.ACTIVE
return result

Go to top
Re: Workbench Arexx port - access the path of an icon
Just can't stay away
Just can't stay away


See User information
@PEB
Thank you , but it must be more complicated , if possible?
from the wiki
Quote:
WINDOWS.ACTIVE
Name of the currently active Workbench window; this will be ' ' if none of Workbench's windows is currently active.

it is the path of a file whose icon has been "left-out" that i am after


/* Query name, position and size of the first icon * shown in the root window. */
GETATTR window.icons.all.0
NAME root
STEM root
 
SAY root
.name
SAY root
.left
SAY root
.top
SAY root
.width
SAY root
.height
SAY root
.type


i was expecting a
root.path here. I onder why it was ot implemented, since you get that path when opening the icon's "information" gui





Edited by JosDuchIt on 2017/9/6 18:25:28
Edited by JosDuchIt on 2017/9/6 18:26:16
Go to top

  Register To Post

 




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )



Polls
Running AmigaOS 4 on?
AmigaOne SE/XE or microA1 12% (26)
Pegasos2 3% (8)
X5000 22% (48)
X1000 14% (30)
A1222 8% (19)
Sam 440/460 18% (40)
Classic PowerPC Amiga 2% (6)
WinUAE emulation 7% (16)
Qemu emulation 9% (21)
Total Votes: 214
The poll closed at 2025/12/1 12:00
6 Comments


Powered by XOOPS 2.0 © 2001-2024 The XOOPS Project