Login
Username:

Password:

Remember me



Lost Password?

Register now!
Main Menu
Who's Online
1 user(s) are online (1 user(s) are browsing Forum)

Members: 0
Guests: 1

more...

Browsing this Thread:   1 Anonymous Users





MUI4 Dtpic class

Joined:
2005/8/17 16:00
From Germany
Group:
Member
Posts: 2201
Offline
http://www.power2people.org/projects/zune-enhancement/

has this:

c) Dtpic class - the private API used by Odyssey needs to be implemented

Is this about new MUI4 attributes like this:
Dtpic.mui/MUIA_Dtpic_Alpha
Dtpic.mui/MUIA_Dtpic_DarkenSelState
Dtpic.mui/MUIA_Dtpic_Fade
Dtpic.mui/MUIA_Dtpic_LightenOnMouse

or are there really additional private attributes?

Posted on: 2014/9/10 13:25
_________________
AROS - Make code, not war
Transfer the post to other applications Transfer


Re: MUI4 Dtpic class

Joined:
2008/1/7 12:41
From Poland
Group:
Dev
Posts: 2923
Offline
If you are referring to what is needed by Odyssey, then the following ones are used in the codes:

Dtpic.mui/MUIA_Dtpic_Alpha
Dtpic.mui/MUIA_Dtpic_DarkenSelState

while those are defined but not used:

Dtpic.mui/MUIA_Dtpic_Fade
Dtpic.mui/MUIA_Dtpic_LightenOnMouse
Dtpic.mui/MUIA_Dtpic_MinWidth
Dtpic.mui/MUIA_Dtpic_MinHeight

Alpha, Fade, MinWidth, MinHeight have comment /* private */. The Darken and Lighten don't have that comment.

Posted on: 2014/9/10 22:51
_________________
Krzysztof

"There is no such thing as software for free. If it is not the user who covers the cost of software creation with money, it is the developer who covers this cost with his own free time."

www.aros3d.org
www.twitter.com/ddeadwood
Transfer the post to other applications Transfer


Re: MUI4 Dtpic class

Joined:
2005/8/17 16:00
From Germany
Group:
Member
Posts: 2201
Offline
Quote:

deadwood wrote:

Dtpic.mui/MUIA_Dtpic_Alpha
Dtpic.mui/MUIA_Dtpic_DarkenSelState
Dtpic.mui/MUIA_Dtpic_Fade
Dtpic.mui/MUIA_Dtpic_LightenOnMouse


Those are documented in the AOS4-MUI4 autodoc. I'm optimistic that I can implement them within some days.

Quote:

Dtpic.mui/MUIA_Dtpic_MinWidth
Dtpic.mui/MUIA_Dtpic_MinHeight


I couldn't find documentation for those.

Posted on: 2014/9/11 3:25
_________________
AROS - Make code, not war
Transfer the post to other applications Transfer


Re: MUI4 Dtpic class

Joined:
2011/6/30 19:50
Group:
Member
Posts: 4095
Offline
Pardon my ignorance, but if they are not defined as such, could it perhaps be that the original author of that bounty tried to tell that support for the inherited properties must/should be implemented ? e.g. properties
#define MUIA_Boopsi_MinHeight 0x80422c93 /* V4 isg ULONG */
#define MUIA_Boopsi_MinWidth 0x80428fb2 /* V4 isg ULONG */

Should be possible to be manipulated directly from within the dtpic class ?

Could they be MorphOS specific properties otherwise perhaps ?
I was unable to locate in MorphOS sdk, Mui(dev) 3.9/4.0 nightly's nor in plain mui 3.8 sdk :S

Posted on: 2014/9/11 4:31

Edited by magorium on 2014/9/11 5:11:03
Transfer the post to other applications Transfer


Re: MUI4 Dtpic class

Joined:
2005/8/17 16:00
From Germany
Group:
Member
Posts: 2201
Offline
Quote:

magorium wrote:
Pardon my ignorance, but if they are not defined as such, could it perhaps be that the original author of that bounty tried to tell that support for the inherited properties must/should be implemented?


Nope, Deadwood has clarified that the needed attributes for Odyssey are MUIA_Dtpic_Alpha and MUIA_Dtpic_DarkenSelState.

BTW: I'm surprised how complex a button of TheBar MCC is:
http://sourceforge.net/p/thebar/code/HEAD/tree/trunk/mcc/button/

Posted on: 2014/9/11 15:36
_________________
AROS - Make code, not war
Transfer the post to other applications Transfer


Re: MUI4 Dtpic class

Joined:
2011/6/30 19:50
Group:
Member
Posts: 4095
Offline
@mazze:
ok, if that means those properties (that can't be tracked for documentation) aren't necessary, then that's a great relief

Quote:
BTW: I'm surprised how complex a button of TheBar MCC is:

Although i don't know where exactly you looked at, be aware that's mcc is a complete toolbar, meaning it supports many buttons next to eachother (ergo lot of spacing and location issues).

Coming from a RAD like Delphi, i am accustomed to loads of variations of button implementations containing all sorts of 'extra's' like flat/unflat mouse hovering, animated labels, animated graphics, side reading labels etc. etc..

So, i kind of think the mcc bar button implementation is pretty clean/straightforward, but i am also aware that this might not have the same impression for an amiganoid developer.

Posted on: 2014/9/12 2:55
Transfer the post to other applications Transfer






You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.

[Advanced Search]


Search
Top Posters
1 paolone
paolone
4282
2 magorium
magorium
4095
3 phoenixkonsole
phoenixkonsole
3887
4 nikolaos
nikolaos
3670
5 deadwood
deadwood
2923
6 ncafferkey
ncafferkey
2574
7 mazze
mazze
2201
8 clusteruk
clusteruk
2055
9 Kalamatee
Kalamatee
2012
10 damocles
damocles
1789
© 2004-2017 AROS Exec