toolbars?

Has there been some change (D4 to D5) in toolbar image handling? Some of my
toolbars that have been transparent now have a white background? Also while
playing with toolbar background color I have managed to get it into the
infinite loop of errors.

Unrelated, I am also seeing this in transcript (I start the fresh image,
open resource browser, sort by the package, and scroll down):

Resource library msmask32.ocx could not be opened ('msmask32.ocx' (16r2: The
system cannot find the file specified.))
Resource library mscomct2.ocx could not be opened ('mscomct2.ocx' (16r2: The
system cannot find the file specified.))

-------- exception stack from the view composer when changing background
color for SUnitToolbar--

18:27:54, 13. travanj 2002: 'Not found: id=15'
ExpandingTreeModel(Object)>>errorNotFound:
[] in ExpandingTreeModel(TreeModel)>>getNodeFor:
IdentityDictionary(LookupTable)>>at:ifAbsent:
ExpandingTreeModel(TreeModel)>>getNodeFor:ifAbsent:
ExpandingTreeModel(TreeModel)>>getNodeFor:
ExpandingTreeModel(TreeModel)>>hasChildren:
TreeView>>onDisplayDetailsRequired:
TreeView(IconicListAbstract)>>nmGetDispInfo:
TreeView>>nmNotify:
ContainerView(View)>>wmNotify:wParam:lParam:
ContainerView(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:evaluate:
InputState>>wndProc:message:wParam:lParam:cookie:
TreeView(ControlView)>>defaultWindowProcessing:wParam:lParam:
TreeView(ControlView)>>wmPaint:wParam:lParam:
TreeView(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:evaluate:
InputState>>wndProc:message:wParam:lParam:cookie:
TreeView(ControlView)>>defaultWindowProcessing:wParam:lParam:
TreeView(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:evaluate:
InputState>>wndProc:message:wParam:lParam:cookie:
TreeView(ControlView)>>defaultWindowProcessing:wParam:lParam:
TreeView(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:evaluate:
InputState>>wndProc:message:wParam:lParam:cookie:
TreeView(ControlView)>>defaultWindowProcessing:wParam:lParam:
TreeView(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:evaluate:
InputState>>wndProc:message:wParam:lParam:cookie:
InputState>>pumpMessage:
InputState>>loopWhile:
InputState>>mainLoop
[] in InputState>>forkMain
ExceptionHandler(ExceptionHandlerAbstract)>>markAndTry
[] in ExceptionHandler(ExceptionHandlerAbstract)>>try:
BlockClosure>>ifCurtailed:
BlockClosure>>ensure:
ExceptionHandler(ExceptionHandlerAbstract)>>try:
BlockClosure>>on:do:

Hi rush,

I was able to do some testing on XP this afternoon and I saw the white
background toolbar problem.

My toolbar that was white in XP had a creation style of #(1140853508 65536)
Changing this to
#(1140851460 65536) fixed it (copied from OA's toolbars).

I was assuming the problem was because the resource had been created in
beta3. I am back working on my w2k machine, and creating a new Shell with
toolbar and inspecting the Toolbar.toolbar resource is showing a creation
style of #(1140853508 65536).

I dont have access to the XP machine to test this, but I assume that this
will again have a white background.

On my w2k machine, both creation styles show the Color face3d background.

Thanks,
Steve

> Has there been some change (D4 to D5) in toolbar image handling? Some of
my
> toolbars that have been transparent now have a white background?

I spent a little time trying to work out how the development tools do it -
all their background colours are set to nil but show up as grey. I couldn't
suss it so I've ended up going through all my shells, setting the top shell
and any container shell backgrounds to "Color face3d", which seems to sort
it all out.  Toolbar backgrounds can then be set to nil or face3d - doesn't
seem to make any difference which.

I've also been tweaking each view's layout to fit in with the new XP layout
format so it has probably been a good exercise anyway.

Ian

Davorin

You wrote in message news:[hidden email]...
> Has there been some change (D4 to D5) in toolbar image handling? Some of
my
> toolbars that have been transparent now have a white background?

Are you running on XP using the XP look-and-feel manifest? If so then a
change in behaviour is that the toolbars pick up the background colour of
the immediate parent. Most of Dolphin's own toolbars are parented by
reference views so that they can be reused, so we found that we had to set
the background colour of the ReferenceView.

>...Also while
> playing with toolbar background color I have managed to get it into the
> infinite loop of errors.

You are running into the PAIs refresh problems, which I expect most people
will experience. It is in need of more work.

>
> Unrelated, I am also seeing this in transcript (I start the fresh image,
> open resource browser, sort by the package, and scroll down):
>
> Resource library msmask32.ocx could not be opened ('msmask32.ocx' (16r2:
The
> system cannot find the file specified.))
> Resource library mscomct2.ocx could not be opened ('mscomct2.ocx' (16r2:
The
> system cannot find the file specified.))
>

These are just complains that the 'Masked Edit' control and some other OCXs
for which wrappers are supplied in D5 are not available on your machine. The
icons for the classes are pulled from the controls themselves. These reports
can safely be ignored.

Regards

Blair

"Blair McGlashan" <[hidden email]> wrote in message
news:[hidden email]...
<snip>
Are you running on XP using the XP look-and-feel manifest?
<snip>

Can you explain what you meant by "XP look-and-feel manifest" - I'm running
on XP and seeing the new look but am not familiar with that term -

jlo

"Jeffrey Odell" <[hidden email]> wrote in message
news:[hidden email]...
>
> "Blair McGlashan" <[hidden email]> wrote in message
> news:[hidden email]...
> <snip>
> Are you running on XP using the XP look-and-feel manifest?
> <snip>
>
> Can you explain what you meant by "XP look-and-feel manifest" - I'm
running
> on XP and seeing the new look but am not familiar with that term -

In order to tell XP that one's application is compatible with XP style one
must include an XML filed called the manifest with the application, either
in the same directory as the app, or in its resources with a particular
resource type and id. We've opted for the separate dolphin.exe.manifest file
(with standard contents, presumably one can put more specialised
configuration in there, but I'm not familiar with the details), as this
allows for easier configuration during setup to make it optional. When
deploying a to-go app. one has the option of using reshacker to include the
manifest in the stub so it does not have to be distributed separately.

Regards

Blair

Jeff,

> > Can you explain what you meant by "XP look-and-feel manifest" - I'm
> running
> > on XP and seeing the new look but am not familiar with that term -
>
> In order to tell XP that one's application is compatible with XP style one
> must include an XML filed called the manifest with the application, either
> in the same directory as the app, or in its resources with a particular
> resource type and id. We've opted for the separate dolphin.exe.manifest
file
> (with standard contents, presumably one can put more specialised
> configuration in there, but I'm not familiar with the details), as this
> allows for easier configuration during setup to make it optional. When
> deploying a to-go app. one has the option of using reshacker to include
the
> manifest in the stub so it does not have to be distributed separately.

You  should also be able to edit the dolphin.exe.manifest file for your
application and use it to turn on the XP style for that too. Remember to
rename the file to "yourapp.exe.manifest" and place it in the same directory
as the EXE.

Best Regards,

Andy Bower
Dolphin Support
http://www.object-arts.com
---
Are you trying too hard?
http://www.object-arts.com/Relax.htm
---

"Blair McGlashan" <[hidden email]> wrote in message
news:[hidden email]...

Hi,

my initial post was relating to XP os, runing in dolphin pro default
enviroment (no deployed app).

Davorin Rusevljan

Oddly enough - now my Dolphin 4.0 is exhibiting XP Look/Feel - was this
expected?  The toolbars have the white background, Tabs have orange bar,
etc.

jlo

Blair McGlashan wrote:

"Jeffrey Odell" <[hidden email]> wrote in message
news:[hidden email]...
> Oddly enough - now my Dolphin 4.0 is exhibiting XP Look/Feel - was this
> expected?  The toolbars have the white background, Tabs have orange bar,
> etc.

How are you starting your images? If you are double clicking them (i.e.
using the file association) then you are actually using the Dolphin 5.0
launcher, which now has the capability to instantiate the correct VM version
for the image it needs to load.

The XP style manifest is associated with the host executable, so if you
don't want the XP look and feel in D4 (which presumably you won't because it
needs a bit of tweaking) then you'll need to create shortcuts that use the
original D4 launcher.

Regards

Blair

I double clicked the image - as I remembered reading it worked now.  I
see where you are headed.

I really like the idea that I can get he XP Look/Feel with D5 - very cool -

jlo

Blair McGlashan wrote:

Hi Blair,

> When
> deploying a to-go app. one has the option of using reshacker to include
the
> manifest in the stub so it does not have to be distributed separately.

FWIW: I was able to add the dolphin.exe.manifest to a ToGo stub using
reshacker and successfully got the XP look and feel.

The "Resource Type" needs to be 24, a "Resource Name" of 1 and a "Resource
Language" of 1033.

Thanks!
Steve