Analog clock MC -- how to produce accurate results?

I'm using Flash 8.
I am trying to program an analog clock movieClip -- if any of
you have seen the UK game show "Countdown", it's a replica of the
Countdown clock. It's a 30-second clock and the second hand runs
from top ("12") to bottom ("6").
My first crack at this has been timeline-based. I've used a
motion tween to animate the hand moving from top to bottom. My
movie is set to run at 12fps, but it's only running at ~11.3fps.
Even though it's a slight deviation, it causes the clock to run
about 32 seconds instead of 30. Note that during the animation, the
CPU usage isn't exceeding about 4%.
I do understand that you can't depend on the Flash Player to
run at a particular framerate.
So I changed the logic behind the clock to use setInterval().
Unfortunately, even my intervals aren't firing at the exact rate
they need to. I've set the interval to 100ms, but it appears to be
firing at 110ms or so. Even changing the intervals to a higher
number (200ms, 500ms) don't produce exact results.
Any ideas or suggestions on how I can make this work?
Thanks,
Curt

When you say “DAQ express” I assume you mean DAQmx, in
LabVIEW 7.0 or later. You could go the route of trying to do precise software
timed stuff, but using WinXP you will always run into the problems that you
mentioned. Hardware timed, will always be more accurate, but setting up the
control may be a bit tricky. To program a hardware timed acquisition you can either
do it explicitly with the DAQmx functions, or you can use the DAQ assistant
(which is an Express VI). With the DAQ assistant once you drop it down it
should be pretty straight forward how to configure it, a window will pop and
you will have to fill in what you want. I would also recommend taking a look at
some of the shipping examples to get a feel for DAQmx programming without using
the DAQ assistant. You can find these examples in LabVIEW by going to: Help
Menu >> Find Example. Then from there: Hardware Input and Output >>
DAQmx >> Analog Generation. If you look at the examples that are Internally
Clocked, those will be the easiest to work with initially. Now I am not too
sure how well this will be for stage control, generally this is done either
with a motion board or if fine enough control is needed FPGA. But with those
examples, it should give you a good starting point to work from.
-GDE

Similar Messages

Spatial Queries Not Always Producing Accurate Results

Hi,
Spatial queries are not always producing accurate results. Here are the issues. We would appreciate any clarification you could provide to resolve these issues.
1. When querying for points inside a polygon that is not an MBR (minimum bounded rectangle), some of the coordinates returned are not inside the polygon. It is as though the primary filter is working, but not the secondary filter when using sdo_relate. How can we validate that the spatial query using sdo_relate is using the secondary filter?
2. SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT returns true when validating geometries even though we find results that are invalid.
3. Illegal geodetic coordinates can be inserted into a table: latitude > 90.0, latitude < -90.0, longitude > 180.0 or longitude < -180.0.
4. Querying for coordinates outside the MBR for the world where illegal coordinates existed did NOT return any rows, yet there were coordinates of long, lat: 181,91.
The following are examples and information relating to the above-referenced points.
select * from USER_SDO_GEOM_METADATA
TABLE_NAME      COLUMN_NAME      DIMINFO(SDO_DIMNAME, SDO_LB, SDO_UB, SDO_TOLERANCE)      SRID
LASTKNOWNPOSITIONS      THE_GEOM SDO_DIM_ARRAY(SDO_DIM_ELEMENT('X', -180, 180, .05), SDO_DIM_ELEMENT('Y', -90, 90, .05))      8307
POSITIONS     THE_GEOM SDO_DIM_ARRAY(SDO_DIM_ELEMENT('X', -180, 180, .05), SDO_DIM_ELEMENT('Y', -90, 90, .05))      8307
Example 1: Query for coordinates inside NON-rectangular polygon includes points outside of polygon.
SELECT l.vesselid, l.latitude, l.longitude, TO_CHAR(l.observationtime,
'YYYY-MM-DD HH24:MI:SS') as obstime FROM lastknownpositions l where
SDO_RELATE(l.the_geom,SDO_GEOMETRY(2003, 8307, NULL,
SDO_ELEM_INFO_ARRAY(1, 1003, 1),
SDO_ORDINATE_ARRAY(-98.20268,18.05079,-57.30101,18.00705,-57.08229,
54.66061,-98.59638,32.87842,-98.20268,18.05079)),'mask=inside')='TRUE'
This query returns the following coordinates that are outside of the polygon:
vesselid : 1152 obstime : 2005-08-24 06:00:00 long : -82.1 lat : 45.3
vesselid : 3140 obstime : 2005-08-28 12:00:00 long : -80.6 lat : 44.6
vesselid : 1253 obstime : 2005-08-22 09:00:00 long : -80.0 lat : 45.3
Example 2a: Using SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT
Select areaid, the_geom,
SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT(the_geom, 0.005) from area where
areaid=24
ResultSet:
AREAID THE_GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO,
SDO_ORDINATES) SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT(THE_GEOM,0.005)
24 SDO_GEOMETRY(2003, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 1003, 1), SDO_ORDINATE_ARRAY(-98.20268, 18.05079, -57.30101, 18.00705, -57.08229, 54.66061, -98.59638, 32.87842, -98.20268, 18.05079)) TRUE
Example 2b: Using SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT
Select positionid, vesselid, the_geom,
SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT(the_geom, 0.005) from positions where vesselid=1152
ResultSet:
POSITIONID VESSELID THE_GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z),
SDO_ELEM_INFO, SDO_ORDINATES) DO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT(THE_GEOM,0.005)
743811 1152 SDO_GEOMETRY(2001, 8307, SDO_POINT_TYPE(-82.1, 45.3, NULL), NULL, NULL) TRUE
743812 1152 SDO_GEOMETRY(2001, 8307, SDO_POINT_TYPE(-82.1, 45.3, NULL), NULL, NULL) TRUE
743813 1152 SDO_GEOMETRY(2001, 8307, SDO_POINT_TYPE(-80.2, 42.5, NULL), NULL, NULL) TRUE
743814 1152 SDO_GEOMETRY(2001, 8307, SDO_POINT_TYPE(-80.2, 42.5, NULL), NULL, NULL) TRUE
Example 3: Invalid Coordinate values found in POSITIONS table.
SELECT p.positionid, p.latitude, p.longitude, p.the_geom FROM positions p
WHERE p.latitude < -180.0
2 lines from ResultSet:
POSITIONID LATITUDE LONGITUDE THE_GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
714915 -210.85408 -79.74449 SDO_GEOMETRY(2001, 8307, SDO_POINT_TYPE(-79.74449, -210.85408, NULL), NULL, NULL)
714938 -211.13632 -79.951256 SDO_GEOMETRY(2001, 8307, SDO_POINT_TYPE(-79.951256, -211.13632, NULL), NULL, NULL)
SELECT p.positionid, p.latitude, p.longitude, p.the_geom FROM positions p
WHERE p.longitude > 180.0
3 lines from ResultSet:
POSITIONID LATITUDE LONGITUDE THE_GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
588434 91 181 SDO_GEOMETRY(2001, 8307, SDO_POINT_TYPE(181, 91, NULL), NULL, NULL)
589493 91 181 SDO_GEOMETRY(2001, 8307, SDO_POINT_TYPE(181, 91, NULL), NULL, NULL)
589494 91 181 SDO_GEOMETRY(2001, 8307, SDO_POINT_TYPE(181, 91, NULL), NULL, NULL)
Example 4: Failure to locate illegal coordinates by querying for disjoint coordinates outside of MBR for the world:
SELECT p.vesselid, p.latitude, p.longitude, p.the_geom,
TO_CHAR(p.observationtime, 'YYYY-MM-DD HH24:MI:SS') as obstime,
SDO_GEOM.RELATE(p.the_geom, 'determine',
SDO_GEOMETRY(2003, 8307, NULL,SDO_ELEM_INFO_ARRAY(1, 1003, 1),
SDO_ORDINATE_ARRAY(-180.0,-90.0,180.0,-90.0,180.0,90.0,
-180.0,90.0,-180.0,-90.0)), .005) relationship FROM positions p where
SDO_GEOM.RELATE(p.the_geom, 'disjoint', SDO_GEOMETRY(2003, 8307,
NULL,SDO_ELEM_INFO_ARRAY(1, 1003, 1),
SDO_ORDINATE_ARRAY(-180.0,-90.0,180.0,-90.0,180.0,90.0,-80.0,90.0,
-180.0,-90.0)),.005)='TRUE'
no rows selected
Carol Saah

Hi Carol,
1) I think the results are correct. Note in a geodetic coordinate system adjacent points in a linestring or polygon are connected via geodesics. You are probably applying planar thinking to an ellipsoidal problem! I don't have time to do the full analysis right now, but a first guess is that is what is happening.
2) The query window seems to be valid. I don't think this is a problem.
3) Oracle will let you insert most anything into a table. In the index, it probably wraps. If you validate, I think the validation routines will tell you is is illegal if you use the signature with diminfo, where the coordinate system bounds are included in the validation.
4) Your query window is not valid. Your data is not valid. As the previous reply stated, you need to have valid data. If you think in terms of a geodetic coordinate system, you will realize that -180.0,-90.0 and 180.0,-90.0 are really the same point. Also, Oracle has a rule that polygon geometries cannot be greater than half the surface of the Earth.
Hope this helps.

How to get accurate results of RGB adjustment layer Shadows in CMYK?

Hi Guys,
This is regarding RGB shadows to CMYK shadows. Most of the times we get the shadows from adjustment layers, when we converting to CMYK shadow as a separate layer it's really difficult to get the results as it in RGB.
In this process we won't get accurate results since we are creating manually. So I would like to know your opinions that how we can get the accurate results?
You can see the following image.
Regards
HARI

I really need to convert to CMYK since I use for packaging.
Am I right to assume that you print in-house then?
So might you not be able to obtain the correct profile for the respective press and just correct the RGB-file as necessary and separate a flattened file at the end?
If you have to to maintain vector- and type-elements you could separate on pdf-creation and subsequently correct those vector elements in Illustrator (if necessary).
Though I have to admit this would hardly be an ideal process as a converted psd-pdf can be a bit complicated.
Another option might be to convert all pertinent elements to a Smart Object in RGB (including the background), keep the vector-/type-elements separate and convert that file to the proper CMYK-space without flattening the SO.
Anyway, handling material from many different sources can of course be quite a challenge depending on the providing parties.

How to get accurate results from sql code ?

Hello everybody,
I have a problem with some portion of my code.
I get more results than I specify in the where clause.
Here is the sample code:
c.gl_acct_id between '110'||'-'||'6890'||'-'||'69000'||'-'||'%'
and '110'||'-'||'7000'||'-'||'67999'||'-'||'%'
For some reason I also get the following results back:
110-6910-51001-001, and 110-6910-51003-001 But I don't need the 51001 and 51003. How do I specify in sql what range I really want. I was sure that the code above is correct. I guess not.
I would appreciate any help,
Thanks,
Sonya

Have you tried using the query either of the following...
1) c.gl_acct_id between '110-6890-69000-000'
and '110-7000-67999-999'
and c.gl_acct_id not like '110-6910-51001-%'
and c.gl_acct_id not like '110-6910-51003-%'
assuming you have only 3 digits at the end of gl_acct.
2)If you know that your acct_id belongs to only 69000 or 67999
then
(c.gl_acct_id LIKE '110-6890-69000-%' OR
c.gl_acct_id LIKE '110-7000-67999-%' )
Plz. let me know if this not what you are looking for.
thanx
rajkiran
Here is the whole script:
select distinct c.gl_acct_id acct_no,
c.gl_acct_desc,
min(a.local_act_beg_bal) local_act_beg_bal,
sum(b.local_act_mtd_dr_amt) debits,
sum(b.local_act_mtd_cr_amt) credits,
nvl(min(a.local_act_beg_bal),0)+sum(nvl(b.local_act_mtd_dr_amt,0))-
sum(nvl(b.local_act_mtd_cr_amt,0)) end_bal
from gl_acct c, gl_acct_bal a, gl_acct_bal b
where c.org_unit_id = '110'
and b.gl_acct_id = c.gl_acct_id
and a.gl_acct_id = c.gl_acct_id
and c.sum_det_ind = 'D'
and c.gl_acct_class_ind in ( 'A' , 'L' , 'Q' , 'I' , 'E' )
and a.year_no = '2001'--:loyear
and a.period_no = '1'--:loperiod
and ( ( b.year_no = '2001'--:hiyear
and b.period_no between '1'--:loperiod
and'13')-- :hiperiod
and c.gl_acct_id between '110'||'-'||'6890'||'-'||'69000'||'-'||'%'
and '110'||'-'||'7000'||'-'||'67999'||'-'||'%'
group by c.gl_acct_id, c.gl_acct_desc
I want to have ability to specify ranges for gl_accoount.
Thanks,
Sonya

How can I change my Analog clock displayed back to a Digital one? (Treo 700wx)

Apparently on its own my phone has changed the format of its clock on the upper right hand corner of the treo screen. The clock used to read digital time but now it reads a clock with an hour hand and a minute hand. No one (Sprint) knows how to change it back to digital time. Help!
Post relates to: Treo 700wx (Sprint)
Message Edited by WyreNut on 04-16-2008 06:16 PM

Take your stylus and tap and hold on the analog clock and you will get a drop down list with two choices analog or digital. Choose digital.
Post relates to: Centro (Sprint)

Old outer join syntax produces different results from new syntax!

I have inherited a query that uses the old outer join syntax but that is yielding correct results. When I translate it to the new outer join syntax, I get the results I expect, but they are not correct! And I don't understand why the old syntax produces the results it produces. Bottom line: I want the results I'm getting from the old syntax, but I need it in the new syntax (I'm putting it into Reporting Services, and RS automatically converts old syntax to new).
Here's the query with the old outer join syntax that is working correctly:
Code Snippet
SELECT   TE = COUNT(DISTINCT T1.ID),
         UE = COUNT(DISTINCT T2.ID),
         PE = CONVERT(MONEY, COUNT(DISTINCT T2.ID)) /
              CONVERT(MONEY,COUNT(DISTINCT T1.ID))
FROM     TABLE T1, TABLE T2
WHERE    T1 *= T2
In this query, much to my surprise, TE <> UE and PE <> 1. However, TE, UE, and PE seem to be accurate!
Here's the query with the new outer join syntax that is working but not producing the results I need:
Code Snippet
SELECT   TE = COUNT(DISTINCT T1.ID),
         UE = COUNT(DISTINCT T2.ID),
         PE = CONVERT(MONEY, COUNT(DISTINCT T2.ID)) /
              CONVERT(MONEY,COUNT(DISTINCT T1.ID))
FROM     TABLE T1 LEFT OUTER JOIN TABLE T2 ON T1.ID = T2.ID
Though not producing the results I need, it is producing what would be expected: TE = UE and PE = 1.
My questions:
1) Can someone who is familiar enough with the old syntax please help me understand why TE <> UE and PE <> 1 in the first query?
2) Can someone please tell me how to properly translate the first query to the new syntax so that it continues to produce the results in the first query?
Thank you very much.

How can we reproduce the issue?
Code Snippet
USE [master]
GO
EXEC sp_dbcmptlevel Northwind, 80
GO
USE [Northwind]
GO
SELECT
TE
= COUNT(DISTINCT T1.OrderID),
UE = COUNT(DISTINCT T2.OrderID),
PE = CONVERT(MONEY, COUNT(DISTINCT T2.OrderID)) /
CONVERT(MONEY,COUNT(DISTINCT T1.OrderID))
FROM
dbo
.Orders T1, dbo.Orders T2
WHERE
T1
.OrderID *= T2.OrderID
SELECT
TE
= COUNT(DISTINCT T1.OrderID),
UE = COUNT(DISTINCT T2.OrderID),
PE = CONVERT(MONEY, COUNT(DISTINCT T2.OrderID)) /
CONVERT(MONEY,COUNT(DISTINCT T1.OrderID))
FROM
dbo
.Orders T1
LEFT OUTER JOIN
dbo.Orders T2
ON T1.OrderID = T2.OrderID
GO
EXEC sp_dbcmptlevel Northwind, 90
GO
Result:
TE
UE
PE
830
830
1.00
TE
UE
PE
830
830
1.00
As you can see, I am getting same results.
AMB

How to get accurate photo printouts using calibrated FlexScan S1932 , Photoshop CS3 and Canon MX925 ? ALL ARE calibrated with i1Pro . WHO SHOULD GOVERN THE PRINTOUT , THE CS3 OR THE PRINTER ?

How to get accurate photo printouts using FlexScan S1932 screen, Photoshop CS3 and Canon MX925 ? ALL ARE calibrated with i1Pro . WHO SHOULD GOVERN THE PRINTOUT , THE CS3 OR THE PRINTER ?

You need to work with the calibration parameters to get a good match from screen to print. There are no fixed values - basically whatever settings produce a match are the right ones.
First, set the white point - luminance and color - so that screen white is a visual equivalent to paper white. You can be very specific about this, with a viewing booth right next to the display and a particular paper as target. Or you can take a more generalistic approach. That too will usually work well, as long as you keep the aim in sight: screen white = paper white.
Don't trust the white point presets. You will usually have to adjust to compensate for your working environment. Make sure you can adjust both along the blue/yellow Kelvin scale and the green/magenta axis. Any given Kelvin value may well be wrong on the green/magenta axis.
Next set a realistic black point. This is important. Monitor manufacturers throw about completely unrealistic contrast ranges that you will never see on paper. A good glossy inkjet paper will be in the vicinity of 250-300:1, or a black point around 0.4 - 0.5 cd/m² if your white point is at 120. If you have a monitor that goes down to, say, 0.2, which most monitors today will, you're in for an unpleasant surprise.
Leave gamma at 2.2. Gamma is remapped from profile to profile and is "invisible" - the net result is always linear. You just want to stay close to native so that the monitor behaves at its best.
If you have a wide gamut monitor soft proofing in Photoshop can be useful. With a standard gamut monitor it's mostly a waste of time since monitor gamut is the limiting one.
Oh, and let Photoshop manage color. Make sure you have the right paper/ink profile and also make sure you have the right paper selected in the printer driver. This controls the total amount of ink.

Filter expression producing different results after upgrade to 11.1.1.7

Hello,
We recently did an upgrade and noticed that on a number of reports where we're using the FILTER expression that the numbers are very inflated. Where we are not using the FILTER expression the numbers are as expected. In the example below we ran the 'Bookings' report in 10g and came up with one number and ran the same report in 11g (11.1.1.7.0) after the upgrade and got two different results. The data source is the same database for each envrionment. Also, in running the physical SQL generated by the 10g and 11g version of the report we get different the inflated numbers from the 11g SQL. Any ideas on what might be happening or causing the issue?
10g report: 2016-Q3......Bookings..........72,017
11g report: 2016-Q3......Bookings..........239,659
This is the simple FILTER expression that is being used in the column formula on the report itself for this particular scenario which produces different results in 10g and 11g.
FILTER("Fact - Opportunities"."Won Opportunity Amount" USING ("Opportunity Attributes"."Business Type" = 'New Business'))
-------------- Physical SQL created by 10g report -------- results as expected --------------------------------------------
WITH
SAWITH0 AS (select sum(case when T33142.OPPORTUNITY_STATUS = 'Won-closed' then T33231.USD_LINE_AMOUNT else 0 end ) as c1,
T28761.QUARTER_YEAR_NAME as c2,
T28761.QUARTER_RANK as c3
from
XXFI.XXFI_GL_FISCAL_MONTHS_V T28761 /* Dim_Periods */ ,
XXFI.XXFI_OSM_OPPTY_HEADER_ACCUM T33142 /* Fact_Opportunity_Headers(CloseDate) */ ,
XXFI.XXFI_OSM_OPPTY_LINE_ACCUM T33231 /* Fact_Opportunity_Lines(CloseDate) */
where ( T28761.PERIOD_NAME = T33142.CLOSE_PERIOD_NAME and T28761.QUARTER_YEAR_NAME = '2012-Q3' and T33142.LEAD_ID = T33231.LEAD_ID and T33231.LINES_BUSINESS_TYPE = 'New Business' and T33142.OPPORTUNITY_STATUS <> 'Duplicate' )
group by T28761.QUARTER_YEAR_NAME, T28761.QUARTER_RANK)
select distinct SAWITH0.c2 as c1,
'Bookings10g' as c2,
SAWITH0.c1 as c3,
SAWITH0.c3 as c5,
SAWITH0.c1 as c7
from
SAWITH0
order by c1, c5
-------------- Physical SQL created by the same report as above but in 11g (11.1.1.7.0) -------- results much higher --------------------------------------------
WITH
SAWITH0 AS (select sum(case when T33142.OPPORTUNITY_STATUS = 'Won-closed' then T33142.TOTAL_OPPORTUNITY_AMOUNT_USD else 0 end ) as c1,
T28761.QUARTER_YEAR_NAME as c2,
T28761.QUARTER_RANK as c3
from
XXFI.XXFI_GL_FISCAL_MONTHS_V T28761 /* Dim_Periods */ ,
XXFI.XXFI_OSM_OPPTY_HEADER_ACCUM T33142 /* Fact_Opportunity_Headers(CloseDate) */ ,
XXFI.XXFI_OSM_OPPTY_LINE_ACCUM T33231 /* Fact_Opportunity_Lines(CloseDate) */
where ( T28761.PERIOD_NAME = T33142.CLOSE_PERIOD_NAME and T28761.QUARTER_YEAR_NAME = '2012-Q3' and T33142.LEAD_ID = T33231.LEAD_ID and T33231.LINES_BUSINESS_TYPE = 'New Business' and T33142.OPPORTUNITY_STATUS <> 'Duplicate' )
group by T28761.QUARTER_YEAR_NAME, T28761.QUARTER_RANK),
SAWITH1 AS (select distinct 0 as c1,
D1.c2 as c2,
'Bookings2' as c3,
D1.c3 as c4,
D1.c1 as c5
from
SAWITH0 D1),
SAWITH2 AS (select D1.c1 as c1,
D1.c2 as c2,
D1.c3 as c3,
D1.c4 as c4,
D1.c5 as c5,
sum(D1.c5) as c6
from
SAWITH1 D1
group by D1.c1, D1.c2, D1.c3, D1.c4, D1.c5)
select D1.c1 as c1, D1.c2 as c2, D1.c3 as c3, D1.c4 as c4, D1.c5 as c5, D1.c6 as c6 from ( select D1.c1 as c1,
D1.c2 as c2,
D1.c3 as c3,
D1.c4 as c4,
D1.c5 as c5,
sum(D1.c6) over () as c6
from
SAWITH2 D1
order by c1, c4, c3 ) D1 where rownum <= 2000001
Thank you,
Mike
Edited by: Mike Jelen on Jun 7, 2013 2:05 PM

Thank you for the info. They are definitely different values since ones on the header and the other is on the lines. As the "Won Opportunity" logical column is mapped to multiple LTS it appears the OBI 11 uses a different alogorthim to determine the most efficient table to use in the query generation vs 10g. I'll need to spend some time researching the impact to adding a 'sort' to the LTS. I'm hoping that there's a way to get OBI to use similar logic relative to 10g in how it generated the table priority.
Thx again,
Mike

How to display the results in order by based on search value

Hi All,
how to display the results in the below order.
CREATE TABLE TEST( SONGID NUMBER, TITLE   VARCHAR2(200))
INSERT INTO TEST(SONGID,TITLE) VALUES (10,'AHMADZAI, MIRWAIS (CA)/ MADONNA (CA)');
INSERT INTO TEST(SONGID,TITLE) VALUES (11,'CICCONE, MADONNA (CA)');
INSERT INTO TEST(SONGID,TITLE) VALUES (12,'DALLIN, MADONNA LOUISE/STOCK');
INSERT INTO TEST(SONGID,TITLE) VALUES (13,'MADONNA');
INSERT INTO TEST(SONGID,TITLE) VALUES (14,'MADONNA (A)/ AHMADZAI, MIRWAIS (C)');
INSERT INTO TEST(SONGID,TITLE) VALUES (15,'MADONNA (CA)');
INSERT INTO TEST(SONGID,TITLE) VALUES (16,'MIRWAIS AHMADZAI, MADONNA');
INSERT INTO TEST(SONGID,TITLE) VALUES (17,'MIRWAIS (CA)/ MADONNA (CA),AHMADZAI');
INSERT INTO TEST(SONGID,TITLE) VALUES (18,'MADONNA (CA),CICCONE');
SELECT *FROM TEST WHERE INSTR (TITLE, 'MADONNA') > 0
output:
SONGID     TITLE
10     AHMADZAI, MIRWAIS (CA)/ MADONNA (CA)
11     CICCONE, MADONNA (CA)
12     DALLIN, MADONNA LOUISE/STOCK
13     MADONNA
14     MADONNA (A)/ AHMADZAI, MIRWAIS (C)
15     MADONNA (CA)
16     MIRWAIS AHMADZAI, MADONNA
17     MIRWAIS (CA)/ MADONNA (CA),AHMADZAI
18     MADONNA (CA),CICCONE
Expected output :
13     MADONNA
14     MADONNA (A)/ AHMADZAI, MIRWAIS (C)
15     MADONNA (CA)
18     MADONNA (CA),CICCONE
...if user searches with 'MADONNA' , I have to display the results like title starts with 'MADONNA' first then rest of the records.
Please let me know is it possible to display the results in that order.
Regards,
Rajasekhar

This may be a bit more accurate:
SQL> SELECT *
2 FROM   TEST
3 WHERE INSTR (TITLE, 'MADONNA') > 0
4 ORDER BY INSTR (TITLE, 'MADONNA')
5           ,TITLE
6 ;
              SONGID TITLE
                  13 MADONNA
                  14 MADONNA (A)/ AHMADZAI, MIRWAIS (C)
                  15 MADONNA (CA)
                  18 MADONNA (CA),CICCONE
                  12 DALLIN, MADONNA LOUISE/STOCK
                  11 CICCONE, MADONNA (CA)
                  17 MIRWAIS (CA)/ MADONNA (CA),AHMADZAI
                  16 MIRWAIS AHMADZAI, MADONNA
                  10 AHMADZAI, MIRWAIS (CA)/ MADONNA (CA)

Is there a way to adjust the size of the analog clock shown on screen?

Ok. this is a minor annoyance but it would be great if someone could tell me how to make the system analog clock (when viewed on screen) can be made smaller? It seems my only other option is to show it as a digital clock or a teeny tiny analg clock on the menu bar.
Thanks in advance.
Mac OS X (10.4.9)
Mac OS X (10.4.9)

.02,
See two views below. Are we talking about the same thing:

Analog clock

how can i get that analog clock that the new BB's have

Eddieclassic wrote:
how can i get that analog clock that the new BB's have
Get a new BlackBerry
Seriously, it is part of the OS on the newer devices, the Storm and Tour.
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Help on query : How to produce columns based on rows?

Hi All,
I have a table table1 with below structure and data
Item     State          Value
A1      MS          100
A1      GOA          3
A1      UP          4
B2      MS          34
B2      GOA          55
B2      PB          3
B2      DL          4
B3      MS          99
B3      TN          1I have an requirement to query this table and generate below output
Item      MS     GOA     UP     PB     DL     TN
A1     100      3     4     0     0     0
B2      34     55     0     3     4     0
B3      99      0     0     0     0     1The issue here is that we can have more State codes hence accordingly the query should dynamically return those number of columns
Is there any way to produce above output? Any help will be appreciated.
Oracle DB Version - Oracle 8i
Thanks in advance!

Hi,
That's called a pivot .
The basic tecnique is something like:
SELECT     item
,     SUM (CASE WHEN state = 'MS' THEN value ELSE 0)     AS ms
,     SUM (CASE WHEN state = 'GOA' THEN value ELSE 0)     AS goa
,     SUM (CASE WHEN state = 'UP' THEN value ELSE 0)     AS up
,     SUM (CASE WHEN state = 'PB' THEN value ELSE 0)     AS pb
,     SUM (CASE WHEN state = 'DL' THEN value ELSE 0)     AS dl
,     SUM (CASE WHEN state = 'TN' THEN value ELSE 0)     AS tn
FROM     table_x
GROUP BY item;but this requires you to know how many states there are, and what they are, when you write the query.
Since you don't, you need to run a preliminary query that will generate a SELECT statement like the one above, or at least the SUM expressions for the variable columns. That's called dynamic SQL , and a technique for doing that is included below. (The example uses COUNT, but any aggregate function, including SUM, will work.)
Another possibility is String Aggregation, where instead of individual columns for each state, you have one huge VARCHAR2 column, formatted to look like separate columns. The tools avaiable for doing that in Oracle 8.1 are pretty poor, however, so I think you're better off with dynamic SQL.
How to Pivot a Table with a Dynamic Number of Columns
This works in any version of Oracle
The "SELECT ... PIVOT" feature introduced in Oracle 11
is much better for producing XML output.
Say you want to make a cross-tab output of
the scott.emp table.
Each row will represent a department.
There will be a separate column for each job.
Each cell will contain the number of employees in
     a specific department having a specific job.
The exact same solution must work with any number
of departments and columns.
(Within reason: there's no guarantee this will work if you
want 2000 columns.)
Case 0 "Basic Pivot" shows how you might hard-code three
job types, which is exactly what you DON'T want to do.
Case 1 "Dynamic Pivot" shows how get the right results
dynamically, using SQL*Plus.
(This can be easily adapted to PL/SQL or other tools.)
NOTE: Using SQL*Plus file I/O, as in this example, is just
one of many ways to do dynamic SQL.
PROMPT     ========== 0. Basic Pivot ==========
SELECT     deptno
,     COUNT (CASE WHEN job = 'ANALYST' THEN 1 END)     AS analyst_cnt
,     COUNT (CASE WHEN job = 'CLERK'   THEN 1 END)     AS clerk_cnt
,     COUNT (CASE WHEN job = 'MANAGER' THEN 1 END)     AS manager_cnt
FROM     scott.emp
WHERE     job     IN ('ANALYST', 'CLERK', 'MANAGER')
GROUP BY     deptno
ORDER BY     deptno
PROMPT     ========== 1. Dynamic Pivot ==========
--     ***** Start of dynamic_pivot.sql *****
-- Suppress SQL*Plus features that interfere with raw output
SET     FEEDBACK     OFF
SET     PAGESIZE     0
SPOOL     p:\sql\cookbook\dynamic_pivot_subscript.sql
SELECT     DISTINCT
     ',     COUNT (CASE WHEN job = '''
||     job
||     ''' '     AS txt1
,     'THEN 1 END)     AS '
||     job
||     '_CNT'     AS txt2
FROM     scott.emp
ORDER BY     txt1;
SPOOL     OFF
-- Restore SQL*Plus features suppressed earlier
SET     FEEDBACK     ON
SET     PAGESIZE     50
SPOOL     p:\sql\cookbook\dynamic_pivot.lst
SELECT     deptno
@@dynamic_pivot_subscript
FROM     scott.emp
GROUP BY     deptno
ORDER BY     deptno
SPOOL     OFF
--     ***** End of dynamic_pivot.sql *****
EXPLANATION:
The basic pivot assumes you know the number of distinct jobs,
and the name of each one. If you do, then writing a pivot query
is simply a matter of writing the correct number of ", COUNT ... AS ..."\
lines, with the name entered in two places on each one. That is easily
done by a preliminary query, which uses SPOOL to write a sub-script
(called dynamic_pivot_subscript.sql in this example).
The main script invokes this sub-script at the proper point.
In practice, .SQL scripts usually contain one or more complete
statements, but there's nothing that says they have to.
This one contains just a fragment from the middle of a SELECT statement.
Before creating the sub-script, turn off SQL*Plus features that are
designed to help humans read the output (such as headings and
feedback messages like "7 rows selected.", since we do not want these
to appear in the sub-script.
Turn these features on again before running the main query.
*/

Robohelp 9 WebHelp - Searching doesn't produce any results.

Hi, I upgraded to RoboHelp 9 last week and now searching in Webhelp doesn't produce any results. I've created a new project, used the sample project, tried generating it to a new folder and results remain the same.
When I select the search tab, the status bar flutters with the "Waiting for file...." displayed indefinetly with the occassion display of the javascript: (void);
Screens shots are from the RH 9 sample project. Results are the same with my projects. CHMs generated work fine!
Any suggestions?

Mary
You added the problem to another thread that was not related as the issue there is the use of HTTPS. I have deleted that post.
You also started a second thread with a the same question. I don't understand how asking the question twice will help so I have locked that thread but created a link to this thread so that anyone with an answer can help you. If there is a reason for starting a second thread, please let me know.
Please just ask once and wait for a reply as this wastes moderator's time that is better used trying to answer questions.
Now to the problem. Searching with Chrome installed works just fine for most people so the problem seems to be local to you. If I have read you correctly, after installing Chrome, the search breaks no matter what browser is used.
Was that checked on other machines or just yours?
IGNORE THIS QUESTION - The answer is YES and that was in the post.
Did you also check that search was broken with the supplied sample projects? I know that works with the three browsers being discussed here?
Where was the help installed when tested by you both standalone and from the application?
Questions 2 and 3 are really only related to problems with Chrome. I have not seen anyone report Chrome also breaking the search in the other browsers. There's more to this than meets the eye as Chrome has not caused that problem for anyone else, or at least, no one has reported it.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Analog Clock in Power Saver mode?

When the E71 is in a power saver mode (black blank screen) with the D-pad button glowing in a slow periodic pattern, you can press the D-pad button and a large digital clock showing the time appears. How can I change that to an analog clock instead?

No, it is not possible to change that on the 3110c.

PS CC 2014 how to get better results from refine edge

In the attached image below you will see "Jesus on the cross" which I want to substitute a new background. On the left is a portion of the unselected image and on the right is the best result I can get via refine edge tool. I have tried all the usual methods such as channels, increasing contrats etc but this is the best I can get. The top thorns had the same problem but what you see now is an hour of manual selection. How do I get a better result - why is it that when the rfine edge brush is swept over such it often only produces transparent results?

I am keep working on this problem today.
I tried Particle Analysis, the result is un-repeatable either. But when I decide to find Straight edge direct from source image,without any process,the angle is more repeatable,Max deviation is 0.03-0.06 degree.It seems my process to the image make thing worse.Then I found the algorithm to find straight is something like linear fit : find all the edge points,linear fit and calculate the angle.
So I run my program for images those pixel resolution is 1280*960,the Max deviation is much lower: 0.008 degree.
If I am right,the best resolution to my problem is to change my camera to higher resolution.
Any advises is appreciate! Thank you!

Analog clock MC -- how to produce accurate results?

Similar Messages

Maybe you are looking for