Last Phindows

Hi,

I found 2 problems:
The first one is, in ‘full window dragging’ mode, windows are not
refreshed correctly when I move these, if MS windows are in front of
them (I want to talk about MS ‘allways on top’ windows).
I don’t remember if this problem was in previous release. I don’t think
so.
The second one is, when we iconify Phindows and then maximize it, the
shelf and task bar go anywhere in the Phindows screen. This problem is
new.

Alain.

Hi,

Another problem!

Using Phindows:

Try to read some help documents with the Help Viewer.
Select a topic. Resize the window. Move the right scrollbar
up and down.

Usuallly within a few minutes phindows crashes.

What is the latest version of phindows?

Michel Benoit

Michel Benoit a écrit :

Hi,

Another problem!

Using Phindows:

Try to read some help documents with the Help Viewer.
Select a topic. Resize the window. Move the right scrollbar
up and down.

Usuallly within a few minutes phindows crashes.

What is the latest version of phindows?

Michel Benoit

It’s not a problem with Phindows, it’s the same version, but rather with
phrelay/photon.

Is the photon/phrelay in patch A suppose to solve this problem
where the Helpviewer crashes phindows?

Michel

Michel Benoit a écrit :

Is the photon/phrelay in patch A suppose to solve this problem
where the Helpviewer crashes phindows?

Michel

According to my tests …, NO!
If you select an item, and move the vertical scrollbar knob, Phindows
still locks.
Alain

Interesting concept: a development environemnt tool that doesn’t let you
use the help documentation.

I currently use my windows machine with phindows for edit and compile
but I have to use my target to read the help files.

I am getting frustrated. I beleive that we paid for phindows.
Is this bug being addressed?

Michel Benoit

This is a known bug and it has been fixed but it but the fix didn’t make it into the patch. It will probably be available for the next release.

Rodney



Previously, Michel Benoit wrote in qdn.public.qnxrtp.photon:

Interesting concept: a development environemnt tool that doesn’t let you
use the help documentation.

I currently use my windows machine with phindows for edit and compile
but I have to use my target to read the help files.

I am getting frustrated. I beleive that we paid for phindows.
Is this bug being addressed?

Michel Benoit

Previously, Rodney Dowdall wrote in qdn.public.qnxrtp.photon:

This is a known bug and it has been fixed but it but the fix didn’t make it into the patch. It will probably be available for the next release.

Rodney

OOPS. I should really proof read more often. The gist of the sentiment is that the fix didn’t make it in to the patch.

Rod


Previously, Michel Benoit wrote in qdn.public.qnxrtp.photon:


Interesting concept: a development environemnt tool that doesn’t let you
use the help documentation.

I currently use my windows machine with phindows for edit and compile
but I have to use my target to read the help files.

I am getting frustrated. I beleive that we paid for phindows.
Is this bug being addressed?

Michel Benoit

Michel,
a workaround for this for now might be for you:

  • Use voyager to read the help files. They are in /usr/help/product
  • Copy /usr/help/product to your windows machine and use your web browser to
    read it there
    Markus

“Michel Benoit” <michel.benoit@saabcom.se> wrote in message
news:3A6D4689.D5F6F990@saabcom.se

Interesting concept: a development environemnt tool that doesn’t let you
use the help documentation.

I currently use my windows machine with phindows for edit and compile
but I have to use my target to read the help files.

I am getting frustrated. I beleive that we paid for phindows.
Is this bug being addressed?

Michel Benoit

Not to be the proverbial “stick in the mud”, but “… probably be available for
the next release” gives me images of me being retired in a nursing home before
the already on its way to being fabled patch “B” hits the streets (according to
the first patch release schedule). Is there not going to be a way, utilizing
this wonderful package mangler/InterNot downUnload thingie that we as the
faithful QNX6 community can enjoy the fruits of these “fixed but not available
until the next release” versions without making your QA & bug tracking a total
living hell? Enquiring minds want to know (so we can schedule really long
vacations if the answer is “go away”).

-Warren “always wanted to go diving in Aussieland” Peece


“Rodney Dowdall” <rdowdall@qnx.com> wrote in message
news:Voyager.010123112459.602133E@rdowdall…
|
| This is a known bug and it has been fixed but it but the fix didn’t make it
into the patch. It will probably be available for the next release.
|
| Rodney
|
|
|
| Previously, Michel Benoit wrote in qdn.public.qnxrtp.photon:
| >
| >
| > Interesting concept: a development environemnt tool that doesn’t let you
| > use the help documentation.
| >
| > I currently use my windows machine with phindows for edit and compile
| > but I have to use my target to read the help files.
| >
| > I am getting frustrated. I beleive that we paid for phindows.
| > Is this bug being addressed?
| >
| > Michel Benoit
| >
|

Warren Peece a écrit :

Not to be the proverbial “stick in the mud”, but “… probably be available for
the next release” gives me images of me being retired in a nursing home before
the already on its way to being fabled patch “B” hits the streets (according to
the first patch release schedule). Is there not going to be a way, utilizing
this wonderful package mangler/InterNot downUnload thingie that we as the
faithful QNX6 community can enjoy the fruits of these “fixed but not available
until the next release” versions without making your QA & bug tracking a total
living hell? Enquiring minds want to know (so we can schedule really long
vacations if the answer is “go away”).

I won’t be so incisive (even if I think that you are right), QRTP is a huge amount
of work and a good work.
Anyway It’s a little too early for QNX to ask us for technical support charge.

Alain.

It seems to be a problem with the shelf update…
two more things that happens.
Yesterday the shelf disapered. Had to remove the .ph file to get it to work
again.
Also if you start a phindows session and resize the background image in
photon get’s updated / stretched or whatever you configurated. but the shelf
stays until you minimize and maximize.


Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote in message
news:3A6C0CA7.82AF8CE5@icbt.com

Hi,

I found 2 problems:
The first one is, in ‘full window dragging’ mode, windows are not
refreshed correctly when I move these, if MS windows are in front of
them (I want to talk about MS ‘allways on top’ windows).
I don’t remember if this problem was in previous release. I don’t think
so.
The second one is, when we iconify Phindows and then maximize it, the
shelf and task bar go anywhere in the Phindows screen. This problem is
new.

Alain.

Warren Peece <warren@nospam.com> wrote:

Not to be the proverbial “stick in the mud”, but “… probably be available for
the next release” gives me images of me being retired in a nursing home before
the already on its way to being fabled patch “B” hits the streets (according to
the first patch release schedule). Is there not going to be a way, utilizing
this wonderful package mangler/InterNot downUnload thingie that we as the
faithful QNX6 community can enjoy the fruits of these “fixed but not available
until the next release” versions without making your QA & bug tracking a total
living hell? Enquiring minds want to know (so we can schedule really long
vacations if the answer is “go away”).

-Warren “always wanted to go diving in Aussieland” Peece

We had some unfortunate timing issues related to the “Fabled Patch A”
that resulted in it being delayed. In the future we are endeavouring
to get stable patches out to customers that will include minor updates
of a handful of things rather than new features which would be made
available in more substantial update packages.

Thomas

“Thomas Fletcher” <thomasf@qnx.com> wrote in message
news:94mpoi$gf0$3@nntp.qnx.com
| Warren Peece <warren@nospam.com> wrote:
| > Not to be the proverbial “stick in the mud”, but “… probably be available
for
| > the next release” gives me images of me being retired in a nursing home
before
| > the already on its way to being fabled patch “B” hits the streets
(according to
| > the first patch release schedule). Is there not going to be a way,
utilizing
| > this wonderful package mangler/InterNot downUnload thingie that we as the
| > faithful QNX6 community can enjoy the fruits of these “fixed but not
available
| > until the next release” versions without making your QA & bug tracking a
total
| > living hell? Enquiring minds want to know (so we can schedule really long
| > vacations if the answer is “go away”).
|
| > -Warren “always wanted to go diving in Aussieland” Peece
|
| We had some unfortunate timing issues related to the “Fabled Patch A”
| that resulted in it being delayed. In the future we are endeavouring
| to get stable patches out to customers that will include minor updates
| of a handful of things rather than new features which would be made
| available in more substantial update packages.
|
| Thomas

Sounds good to me!

-Warren “see I’m not so hard to get along with” Peece