Can a Forge Cleric use Artisan’s Blessing to convert metal into currency?

The Forge Domain cleric’s Artisan’s Blessing Channel Divinity option (XGtE, p. 19) states:

You conduct an hour-long ritual that crafts a nonmagical item that must include some metal: a simple or martial weapon, a suit of armor, ten pieces of ammunition, a set of tools, or another metal object […]

The thing you create can be something that is worth no more than 100 gp. As part of this ritual, you must lay out metal, which can include coins, with a value equal to the creation.

I understand that it may be ambiguous whether or not I could make a pile of gold, but a gold bar should work just fine.

Is there any reason I can’t convert used weapons into gold bars, to receive 100% of their market value?

Are there any rules that indicate that selling a gold bar results in some kind of loss in value?

XMVector3Project is giving offset values when trying to convert world space coordinates to screen space coordinates

I am trying to convert world space coordinates to screen space coordinates for a 2D game so I can work on collisions with the edges of the window.

enter image description here

The code I am using to convert world space coordinates to screen space is below

float centerX = boundingBox.m_center.x; XMVECTORF32 centerVector = { centerX, 0.0f, 0.0f, 0.0f };   Windows::Foundation::Size screenSize = m_deviceResources->GetLogicalSize(); //the matrices are passed in transposed, so reverse it DirectX::XMMATRIX projection = XMMatrixTranspose(XMLoadFloat4x4(&m_projectionMatrix)); DirectX::XMMATRIX view = XMMatrixTranspose(XMLoadFloat4x4(&m_viewMatrix)); worldMatrix = XMMatrixTranspose(worldMatrix);  XMVECTOR centerProjection = XMVector3Project(centerVector, 0.0f, 0.0f, screenSize.Width, screenSize.Height, 0.0f, 1.0f, projection, view, worldMatrix);  float centerScreenSpace = XMVectorGetX(centerProjection);  std::stringstream ss; ss << "CENTER SCREEN SPACE X: " << centerScreenSpace << std::endl; OutputDebugStringA(ss.str().c_str()); 

I have a window width 1262. The object is positioned at (0.0, 0.0, 0.0) and the current screen space X coordinate for this position is 631 which is correct. However, the problem occurs when I move the object towards the edges of the screen.

enter image description here

When I move the object to the left, the current screen space X coordinate for this position is 0.107788 when realistically it should be well above 0 as the center point is still on the screen and nowhere near the edge. The same happens on when moving the object to the right.

The screen size in pixels is correct, but something thinks that the screen has a premature cut-off like in the image below. It seems that the red dotted lines are the edges of the window when they’re not. I can fix this by adding an additional offset but I don’t believe that is the correct way to fix it and would like to know where I’m going wrong.

enter image description here

Does anyone know why the coordinates are incorrect?

Convert Helios-44 m39 mount to use it as magnifying lens

I own a Helios-44, it has a m42 screw mount and does not own a focus ring. Is it possible to use this lens as a magnifying lens for analog prints, with a standard photo enlarger for analog prints. With a m42 to m39 adapter it could be screwed on the enlarger, will it give a decent quality compared to real magnifying lenses like a lower quality 50mm 3.5 Rodenstock Trinar.

enter image description here enter image description here

Want to convert a hard drive from ntfs to fat (not fat 32) [on hold]

I have a Samsung device and I want to connect an external hard drive in it with otg put the problem is the hard drive isn’t readable om my phone …I searched on internet for a solution and I found a tutorial that says that I have to convert the file system of the hard drive from ntfs to fat but the problem is there is no tutorial for converting ntfs to fat not(fat 32) because fat 32 isn’t readable on my android device … So you can please help me to make my external hard drive readable on my android device… And thanks…

SSIS column cannot convert between unicode and non-unicode string data types

I am transferring a table from SQL Server to PDA Server. This is my data flow:

ADO NET Source —> OLE DB Destination

All of the columns in my source table are varchars and so when I created my destination table, I made sure that they had the same data types. So both tables have varchar data types for all columns.

However, I am still getting the error: Column “col1” cannot convert between unicode and non-unicode string data types. The weird thing is that if I replace my OLE DB Destination with a ADO Net Destination, it seems to work however, I want to use OLE DB so that I can specifying things such as rows per batch.

Can anyone help?

#Error in SSRS, Tried CSTR to convert but no impact

Kindly help!

=IIF(ISNOTHING(CStr(Fields!ExpAccountDisplay.Value)) OR CStr(Fields!ExpAccountDisplay.Value) = 0 OR CStr(Fields!ExpAccountDisplay.Value) = “”,”No Exp Account”,CStr(Fields!ExpAccountDisplay.Value))

The data type of field is uniqueidentifier.

The Value to the field from application is Advertising Expense – 6100

Convert HTML input string to JavaScript Array literal

I am trying to accept JavaScript array literals in an HTML text input.

The problem is that HTML text inputs are captured as strings, such that an input of ['name', 'who', 1] becomes "['name', 'who', 1]".

My intention is for the following samples to yield the corresponding outputs.

"['river',"spring"]"        //  ["river","spring"]  "[{key:'value'},20,'who']"  //  [{"key":"value"},20,"who"] 

The way I worked around the problem is by using eval in the code snippet below:

const form = document.querySelector('.form');      const inputField = document.querySelector('.input');     const btnParse= document.querySelector('.btn');      const out = document.querySelector('.out');           form.addEventListener('submit', (e)=> {          e.preventDefault();         try {             parsed = eval(inputField.value);          if(Array.isArray(parsed)) {                  out.textContent = JSON.stringify(parsed);         } else throw new Error('input is  not a valid array' );       } catch(err) {         out.textContent = `Invalid input: $  {err.message}`;       }      }); 
 <form class="form">          <fieldset>          <legend>Enter array to parse</legend>               <input class="input" type="text">               <input class="btn" type="submit" value="parse">         </fieldset>     </form>     <div>          <p class="out">        </p>      </div>        

My solution, however, allows for the execution of any Javascript code inputted into the text field, which is a huge vulnerability.

What alternative way is there to converting JavaScript array literal HTML text inputs into JS array objects without using eval?